Currently, our FE Build inherits the default values for chunkLoadingGlobal and uniqueName directly from Webpack, which can lead to runtime and chunk conflicts when clientlibs are deployed to third-party applications or other AEM projects using Webpack.
To address this, we want to define our own FE Build-specific defaults for these properties, so that any project using our build system will automatically benefit from safer, isolated chunk and runtime handling—without inheriting the potentially conflicting Webpack defaults.
Importantly, this change should still allow projects to override these defaults as needed.
The configuration hierarchy should be:
Webpack → NC FE Build defaults → Project config
This ensures that by simply updating FE Build, projects get the improved defaults, but retain full flexibility to customize as required.
https://webpack.js.org/configuration/output/#outputchunkloadingglobal
https://webpack.js.org/configuration/output/#outputuniquename
Currently, our FE Build inherits the default values for
chunkLoadingGlobalanduniqueNamedirectly from Webpack, which can lead to runtime and chunk conflicts when clientlibs are deployed to third-party applications or other AEM projects using Webpack.To address this, we want to define
our own FE Build-specificdefaults for these properties, so that any project using our build system will automatically benefit from safer, isolated chunk and runtime handling—without inheriting the potentially conflicting Webpack defaults.Importantly, this change should still allow projects to override these defaults as needed.
The configuration hierarchy should be:
Webpack → NC FE Build defaults → Project configThis ensures that by simply updating FE Build, projects get the improved defaults, but retain full flexibility to customize as required.
https://webpack.js.org/configuration/output/#outputchunkloadingglobal
https://webpack.js.org/configuration/output/#outputuniquename