sideEffects flag disrupts treeshaking
See original GitHub issueWebpack sideEffects doesn’t compile properly in latest version of Webpack 4.25.1
.
Removing it fixes this issue.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Tree Shaking - webpack
Clarifying tree shaking and sideEffects ... The sideEffects and usedExports (more known as tree shaking) optimizations are two different things. sideEffects is ...
Read more >Side effects flag for tree shaking · Issue #744 - GitHub
The package.json should have a "sideEffect": false flag to enable tree shaking. Screenshots. Bundle size with sideEffects flag. As you can see, ...
Read more >Question about tree-shaking / side-effects - Stack Overflow
I am trying to reduce bundle size of my nextjs project and I have some problem with tree shaking. Let me explain. I...
Read more >Tree Shaking React Native Apps - Klarna Engineering
Tree Shaking is a form of dead-code elimination related specifically to removal of unused exports. If we would concatenate all modules, unused ...
Read more >Tree Shaking Examples - Katerina198b
A side effect is defined as a code that performs a special behaviour when imported, other than exposing one or more exports. Let's...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@petrjaros, @Cheprer glad we’ve figured it out. Using newer versions of monet is highly recommended because of this implicit fiddling with system prototypes. Can we close this, as this doesn’t seem to be the cause of problem anymore ?
Closing this, as the problem was somewhere else.