Sam PoderandGitHub e71934a17f [turbopack] Drop unused exports from a CJS module (#95716) ...

This PR introduces two new things: a pass of the analyzer that
recognises exports from CJS modules (in the form of `exports.foo`, see
`analyze_cjs_exports`) and then a CodeGen that reads `export_usage_info`
to remove CJS exports that are not used.

This PR does not add anything additionally to `export_usage_info`, so
this means that we only trim from modules that are imported with `import
{ foo } from "bar"`. The CodeGen depends on the output of
`analyze_cjs_exports` for the locations of exports, whether it is safe
to drop exports (its pretty conservative), and also whether `__esModule`
is present.

2026-07-20 15:51:46 -07:00

..

1ece_tests_snapshot_cjs-remove-unused-exports_this-in-arrow_input_index_1a7v9ht.js

…

1jsg_tests_snapshot_cjs-remove-unused-exports_this-in-arrow_input_0tvvz6j._.js

…

1jsg_tests_snapshot_cjs-remove-unused-exports_this-in-arrow_input_0tvvz6j._.js.map

…

1jsg_tests_snapshot_cjs-remove-unused-exports_this-in-arrow_input_index_1a7v9ht.js.map

…