404 not found on two build related .map files

Created on 30 January 2024, 11 months ago
Updated 26 February 2024, 10 months ago

Problem/Motivation

/libraries/wet-boew/js/purify.js.map
and
/profiles/wxt/modules/custom/wxt_ext/wxt_ext_editor/css/cke5-theme.css.map

Error message in the dblog:

Type	page not found
Date	Monday, January 29, 2024 - 22:52
User	admin
Location	http://wxt-demo.localhost/libraries/wet-boew/js/purify.js.map
Referrer	
Message	/libraries/wet-boew/js/purify.js.map
Severity	Warning
Type	page not found
Date	Monday, January 29, 2024 - 22:52
User	admin
Location	http://wxt-demo.localhost/profiles/wxt/modules/custom/wxt_ext/wxt_ext_editor/css/cke5-theme.css.map
Referrer	
Message	/profiles/wxt/modules/custom/wxt_ext/wxt_ext_editor/css/cke5-theme.css.map
Severity	Warning

Steps to reproduce

Install WxT, start using the editor. Edit some content

Proposed resolution

TBD

Remaining tasks

Review these map files.

User interface changes

TBD

API changes

TBD

Data model changes

N/A

🐛 Bug report
Status

Active

Version

5.1

Component

Code

Created by

🇨🇦Canada joseph.olstad

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @joseph.olstad
  • 🇨🇦Canada danrod Ottawa

    I'm seeing the same issue here, it looks like the *.map files are being invoked from these files:

    ./html/libraries/wet-boew/js/wet-boew.js line 1456:

    //# sourceMappingURL=purify.js.map

    And

    ./html/profiles/wxt/modules/custom/wxt_ext/wxt_ext_editor/css/cke5-theme-gcweb.css line 19436:

    /*# sourceMappingURL=cke5-theme.css.map */

    Can we try to re-build the assets and include the map files? I tried to do this myself but I couldn't find the cke5-theme.sass file for that.

  • 🇨🇦Canada joseph.olstad

    hmm, I bet if we were using the wet-boew.min.js the map files would not be used, it would also be compressed.
    The source file is helpful for debugging however normally we'd likely prefer the wet-boew.min.js

  • 🇨🇦Canada joseph.olstad

    Line number 80 and 81 from wxt_library.module

      $config = \Drupal::config('wxt_library.settings');
      $variant = ($config->get('minimized.options')) ? 'minified' : 'source';
    

    This shows that there's a configuration setting to use, simply change to the minified option and the map errors should go away.

  • 🇨🇦Canada joseph.olstad

    Ok I found the minimize mode option setting:

  • 🇨🇦Canada SKAUGHT

    aged, odd process cycle:
    Drupal 10.1's own css/js aggregation engine support minification in a new way: we should rely on it more.

    this is an odd spot to put a dev/prod swtich. complicated testing, etc. can we work torward removal/simplify?

  • 🇨🇦Canada joseph.olstad

    @SKAUGHT, yes by all means, if we can modernize this and take advantage of D10.1's css/js aggregation support of minification we should for sure do so! Sounds great!

  • 🇨🇦Canada sylus

    wxt_library assets are pulled in from wet-boew assets and are not under Drupal's control which is why they can't fall under Drupal's minification process because the assets are hosted externally and have their own minification process.

Production build 0.71.5 2024