You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can also run yarn and yarn build to rebuild the output
Expected Behavior
We'd expect Rollup to de-dupe the import alias similar to how it behaves with preserveModules: false (e.g. index$1)
import * as index from './module-a/v1/index.js';
export { index as ModuleA_V1 };
import * as index$1 from './module-b/v1/index.js';
export { index$1 as ModuleB_V1 };
…at using nested export star statements (#3435)
* Add failing test for barrel exports #3365
* Update expected outputs
* Fix expected output
* Set chunkOrExternalModule.variableName in deconflictImportsEsm
* Dconflict deps when preserveModules is true
* Update system-exports-wrap-pure-annotation
* Actually use preserveModules flag
* Only deconflict deps in esm to minimize impact
* Update tests expected output
* Update test, add more context to comment
Search terms: export star, reexport, re-export, nested modules, preserveModules
When using
preserveModules
, we're seeing an issue handling nested module re-exporting usingexport *
as shown below.How Do We Reproduce?
Minimal reproduction: https://github.com/kamranayub/rollup-bug-reexporting-preserveModules
dist/index.js
yarn
andyarn build
to rebuild the outputExpected Behavior
We'd expect Rollup to de-dupe the import alias similar to how it behaves with
preserveModules: false
(e.g.index$1
)Actual Behavior
Rollup generates a duplicate import alias:
This will result in an error when consumed:
See: https://github.com/kamranayub/rollup-bug-reexporting-preserveModules/blob/master/dist/index.js
The text was updated successfully, but these errors were encountered: