Files
Niklas MischkulnigandGitHub bc385a0c7b Turbopack: correct export usage in EcmascriptModulePartReference (#80526)
With 
```js
export { x as c } from "./x.js";
```
you get these modules:

```js
"input/index.js [test] (ecmascript)"
--> a EsmAssetReference but `apply_reexport_tree_shaking` returns an `EcmascriptModuleFacadeModule`
"input/node_modules/package-named/x.js [test] (ecmascript, facade) <export x as c>"
--> a EcmascriptModulePartReference that was previously always `ExportUsage::All`
"input/node_modules/package-named/x.js [test] (ecmascript)"
```

i.e. it previously would never tree shake anything from `x.js` in this case, if there was a used renaming-reexport in front of it.
2025-06-17 11:28:05 +02:00

4 lines
42 B
JavaScript

import { a0 } from 'lib'
console.log(a0)