Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"export * from" breaks tree shaking
See original GitHub issueBug report
What is the current behavior? One of our dependencies re-exports the index.js file of https://www.npmjs.com/package/@material-ui/core like so:
export * from '@material-ui/core';
We would expect Webpack 5 to tree shake this as per https://webpack.js.org/blog/2020-10-10-webpack-5-release/#nested-tree-shaking, however, inspecting the build shows that the ENTIRE @material-ui/core is included in the bundle - even if no modules from this package are used.
If the current behavior is a bug, please provide the steps to reproduce.
- Set up basic webpack project
- In a dependency in node_modules, re-export
@material-ui/coreas per the above - Create production build
- Inspect generated chunks
What is the expected behavior?
Webpack should deep-shake the re-exported package.
Other relevant information: webpack version: 5.40.0 Node.js version: 14 Operating System: OSX Catalina Additional tools:
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
export *is not related to the export-default-from proposal. Nonetheless all of these constructs are supported for tree shaking.Could you please provide a complete reproduction for the problem?
Hm, looking into it, it seems like this is non-standard syntax (still a proposal - https://github.com/tc39/proposal-export-default-from), I suppose that is the reason it does not work?