How does tree shaking actually work in Webpack, and why is our production build still including unused exports from third-party npm packages that we only import partial functions from?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How does tree shaking actually work in Webpack, and why is our production build still including unused exports from third-party npm packages that we only import partial functions from?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
Webpack tree shaking official documentation usedExports sideEffects package exports ES modules Google ↗
Webpack tree shaking third party npm packages lodash lodash-es CommonJS official documentation Google ↗
- webpack · webpack.js.org
- webpack.js.org/src/content/guides/tree-shaking.mdx at main · webpack/webpack.js.org · github.com
- Package exports · webpack.js.org
- Tree-shaking · eui.elastic.co
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Webpack tree shaking official documentation usedExports sideEffects package exports ES modules OBSERVED | Google ↗ AI Mode ↗ | — | Consequence | — | — | 1x of 1 | |
Webpack tree shaking third party npm packages lodash lodash-es CommonJS official documentation OBSERVED | Google ↗ AI Mode ↗ | — | Other / navigational | — | — | 1x of 1 |