Not a webpack bundle unhandled rejection on every chunk #10

Activity

1. developit commented on Dec 14, 2020

   

   developit

   on Dec 14, 2020

   Owner

   More actions

   Hiya - this seems the same as the second issue mentioned in #7.
   Are you able to share your Webpack configuration - in particular the mode, target and output options?
2. developit

   added

   needs more infoMore information is needed to diagnose.More information is needed to diagnose.

   on Dec 14, 2020
3. keepitterron commented on Dec 14, 2020

   

   keepitterron

   on Dec 14, 2020

   Author

   More actions

   Absolutely!

   {
     "entry":{
       ...multiple entries
     },
     "output":{
        "path":"/Users/claudio/Projects/loom/dist/webpack",
        "publicPath":"https://cdn.loom.com/assets/",
        "filename":"js/[name]-[contenthash].js"
     },
     "devtool":false,
     "module":{
        "rules":[...rules]
     },
     "optimization":{
        "moduleIds":"hashed",
        "splitChunks":{
           "cacheGroups":{
              "default":false,
              "commons":{
                 "name":"commons",
                 "test":{
                    
                 },
                 "chunks":"all",
                 "minChunks":3
              }
           }
        },
     },
     "plugins":[...plugins],
     "resolve":{...aliases only},
     "mode":"production"
   }
   

   babel.config contains preset/react and preset/env with no modules nor target options set.

   👍React with 👍1Reacted by Jason Miller

   ❤️React with ❤️1Reacted by Jason Miller
4. developit commented on Dec 18, 2020

   

   developit

   on Dec 18, 2020

   Owner

   More actions

   Awesome, thanks for this. I will try to set up a test case. I likely missed some bundle parsing cases for multi-entry since I avoid using multi-entry whenever possible for performance reasons.

   🎉React with 🎉1Reacted by Claudio Semeraro
5. keepitterron commented on Dec 20, 2020

   

   keepitterron

   on Dec 20, 2020

   Author

   More actions

   Oh that's very interesting. I can intuitively understand why would it be a performance drain, do you have any links where I can learn more (multi entry webpack)? 🙏
   I'll do some digging of my own in the meanwhile :)
6. developit commented on Dec 21, 2020

   

   developit

   on Dec 21, 2020

   Owner

   More actions

   @keepitterron it's a little buried in the docs, but there now:
   https://webpack.js.org/plugins/module-concatenation-plugin/#optimization-bailouts
7. 3zzy commented on Dec 28, 2020

   

   3zzy

   on Dec 28, 2020

   More actions

   We bundle multiple separate 'apps' so we definitely need multiple entries, not something we can avoid unfortunately.

   👍React with 👍1Reacted by Dave Buchhofer
8. developit commented on Feb 24, 2021

   

   developit

   on Feb 24, 2021

   Owner

   More actions

   For those hitting this issue, you can disable automatic modernization via new OptimizePlugin({ modernize: false }). This improves performance, but will use the unmodified ES5 source of most npm modules since they do not publish modern code.