Looking for a workaround for this webpack5 bug, specifically how to get chunkFilename to work as before with [contenthash:9] or at least [contenthash]. Or some other way to name the built chunks uniquely and content-dependently, without also hashing the entries (which in turn would cause jsxPaths to be unpredictable and harder to handle).
Example from webpack config for the build-components step:
In addition to weakening the automatic cache(busting) behaviour, this presents a problem if there is an entry in one of the entryDirs with the same name (without extension, and case-insensitive) as a chunkDir, for example the entry src/main/resources/react4xp//Movie.js while at the same time src/main/resources/react4xp/movie is a chunkDir. Builds if there's no such name collision, but should be fixed anyway.
Looking for a workaround for this webpack5 bug, specifically how to get
chunkFilename
to work as before with[contenthash:9]
or at least[contenthash]
. Or some other way to name the built chunks uniquely and content-dependently, without also hashing the entries (which in turn would cause jsxPaths to be unpredictable and harder to handle).Example from webpack config for the build-components step:
In addition to weakening the automatic cache(busting) behaviour, this presents a problem if there is an entry in one of the entryDirs with the same name (without extension, and case-insensitive) as a chunkDir, for example the entry src/main/resources/react4xp//Movie.js while at the same time src/main/resources/react4xp/movie is a chunkDir. Builds if there's no such name collision, but should be fixed anyway.