You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, each plugin handles JavaScript and CSS minification through individual Webpack configurations. This approach requires manual updates to CopyWebpackPlugin patterns whenever new assets are added or renamed, creating unnecessary maintenance overhead.
For example, introducing a new JavaScript file currently requires updating the CopyWebpackPlugin patterns in the relevant plugin's configuration by adding the following:
Reduces configuration duplication for plugins like Performance Lab, Embed Optimizer, and Image Prioritizer, where Webpack configs exist solely for asset minification.
Note: The configuration could be further refined to target assets only for the specific plugin being built during production builds if needed.
The text was updated successfully, but these errors were encountered:
Currently, each plugin handles JavaScript and CSS minification through individual Webpack configurations. This approach requires manual updates to
CopyWebpackPlugin
patterns whenever new assets are added or renamed, creating unnecessary maintenance overhead.For example, introducing a new JavaScript file currently requires updating the
CopyWebpackPlugin
patterns in the relevant plugin's configuration by adding the following:To streamline this process, we could introduce a generalized Webpack configuration that:
build
directory (typically library files copied fromnode_modules
) and already-minified assets.Below is a potential Webpack configuration:
Benefits:
Note: The configuration could be further refined to target assets only for the specific plugin being built during production builds if needed.
The text was updated successfully, but these errors were encountered: