Feature to document
output.chunkLoadingGlobal
Author(s)
Additional information
Previously on Webpack 4 we had a decently documented output.jsonpFunction output configuration option.
Looks like peoples says that Webpack 4 output.jsonpFunction is now Webpack 5 output.chunkLoadingGlobal:
But the documentation in Webpack 5 is pretty poor:
I don't understand the difference between jsonpFunction and chunkLoadingGlobal.
Could you explain in the documentation that exactly is chunkLoadingGlobal and most importantly: What problem does is solves? 🤔
For example I have an erratic TypeError: webpack_modules[moduleId] is not a function and I'm not sure if chunkLoadingGlobal may solve the problem 🤔
Should we systematically define a specific chunkLoadingGlobal when we run multiple Webpack instances on the same page? Why?
Is this 2017 article still https://medium.com/@cliffers/how-to-run-multiple-webpack-instances-on-the-same-page-and-avoid-any-conflicts-4e2fe0f016d1 still relevant?
Feature to document
output.chunkLoadingGlobalAuthor(s)
Additional information
Previously on Webpack 4 we had a decently documented
output.jsonpFunctionoutput configuration option.Looks like peoples says that Webpack 4
output.jsonpFunctionis now Webpack 5output.chunkLoadingGlobal:But the documentation in Webpack 5 is pretty poor:
I don't understand the difference between
jsonpFunctionandchunkLoadingGlobal.Could you explain in the documentation that exactly is
chunkLoadingGlobaland most importantly: What problem does is solves? 🤔For example I have an erratic
TypeError: webpack_modules[moduleId] is not a functionand I'm not sure ifchunkLoadingGlobalmay solve the problem 🤔Should we systematically define a specific
chunkLoadingGlobalwhen we run multiple Webpack instances on the same page? Why?Is this 2017 article still https://medium.com/@cliffers/how-to-run-multiple-webpack-instances-on-the-same-page-and-avoid-any-conflicts-4e2fe0f016d1 still relevant?