Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #48154, comment 73


Ignore:
Timestamp:
03/03/2020 05:28:15 PM (5 years ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #48154, comment 73

    initial v1  
    66> We should extend it for combined asset files and have one for `development` and one for `production`.
    77
    8 This is pretty much how it works now, but is not very straightforward, it's hard to "see" it. The dev version of `script-loader-packages.php` is in /src and is committed. The production version is generated every time `npm run build` (or `grunt build`) is run.
     8This is pretty much how it works now, but is not very straightforward, it's hard to "see" it. The dev version of `script-loader-packages.php` is in /src and is committed. The production version is generated every time `npm run build` (or `grunt build`) is run, and is in /build.
    99
    1010> They would be loaded conditionally, similar to how assets are registered. The only blocker is that the name for the output file is hardcoded in the webpack plugin so we need to allow some customization as proposed by @azaozz in https://github.com/WordPress/gutenberg/issues/20562.