Sam PoderandGitHub e90189b940 [turbopack] Rename turbopackTreeShaking to turbopackModuleFragments (#95978) ...

This has been causing a lot of confusion when contributors have been
debugging tree shaking, eg.
https://github.com/vercel/next.js/issues/95698 and the linked issues.
Turbopack's standard tree-shaking features are controlled through the
`turbopackRemoveUnusedExports` and `turbopackRemoveUnusedImports`
options which default to true.

2026-07-20 18:14:11 -07:00

..

input-source-map

[turbopack] Sort modules in chunks to reduce duplicates (#94961)

2026-06-19 00:07:59 -07:00

input-source-map-merged

[turbopack] Rename turbopackTreeShaking to turbopackModuleFragments (#95978)

2026-07-20 18:14:11 -07:00

invalid

Turbopack: switch from base40 to base38 hash encoding (remove ~ and . from charset) (#91832)

2026-03-25 08:27:30 +01:00

merged-unicode

[turbopack] Rename turbopackTreeShaking to turbopackModuleFragments (#95978)

2026-07-20 18:14:11 -07:00

react-compiler

[turbopack] Sort modules in chunks to reduce duplicates (#94961)

2026-06-19 00:07:59 -07:00