We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
export *
@mohd-akram and I incorrectly deduced that duplicate named exports resulted in those exports being excluded.
However, this is not always the case!
With the following code: a.mjs
a.mjs
export function foo() { return 'a' }
b.mjs
export function foo() { return 'b' }
dupe.mjs
// the order here doesn't matter! export * from './a.mjs' export { foo } from './b.mjs'
test.mjs
import { foo } from './dupe.mjs' console.log('out:', foo())
> node test.mjs out: b
dupe.mjs should export foo from b.mjs. This is because explicitly named exports DO override export * exports.
foo
The text was updated successfully, but these errors were encountered:
Nice.
Sorry, something went wrong.
It continues
Will it ever end!
No. https://github.com/tc39/proposal-defer-import-eval
1c6f7b0
Successfully merging a pull request may close this issue.
@mohd-akram and I incorrectly deduced that duplicate named exports resulted in those exports being excluded.
However, this is not always the case!
With the following code:
a.mjs
b.mjs
dupe.mjs
test.mjs
dupe.mjs
should exportfoo
fromb.mjs
. This is because explicitly named exports DO overrideexport *
exports.The text was updated successfully, but these errors were encountered: