issues in reexport #1055
Closed
IWANABETHATGUY
started this conversation in
General
Replies: 1 comment
-
Explicit named export has higher priority 1.// main.js
import { a } from './foo'
console.log(a)
// foo.js
export const a = 'foo';
export * from './bar'
// bar.js
export const a = 'bar' Expected// foo.js
export const a = 'foo';
// main.js
console.log(a) Explicit named export has higher priority 2.// main.js
import { a } from './foo'
console.log(a)
// foo.js
export { a } from './baz'
export * from './bar'
// bar.js
export const a = 'bar'
// baz.js
export const a = 'baz' Expected// foo.js
export const a = 'baz';
// main.js
console.log(a) Conflicted name by re-export all should be hidden// main.js
export * from './foo'
export * from './bar'
// foo.js
export const a = 'foo'
export const b = 'foo'
// bar.js
export const a = 'bar' Expected// foo.js
export const b = 'foo'; |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
reexport have duplicate
File: example/index.mjs
File: example/bar.mjs
File: example/foo.mjs
File: example/result.mjs
Summary
foo.mjs
andresult.mjs
have exportedb
execute
node index.mjs
got:
only edit
bar.mjs
Now both
bar.mjs
,foo.mjs
andresult.mjs
have exportedb
execute it again
got nothing in output
Beta Was this translation helpful? Give feedback.
All reactions