Repository navigation
Weird behaviour with export #791
Description
Hello
I was having trouble using this (with the Webpack loader) in my project. I ended up finding that the problem was in some files where I had code like this:
import funcA from './funcA'
import funcB from './funcB'
export {
funcA,
funcB,
}With that, some other module that would try to import and use funcA would not work (would get undefined or something like it). It seems that in one point the identifiers were changed but not in the other point.
When I changed the code to this, it worked:
export { default as funcA } from './funcA'
export { default as funcB } from './funcB'I'm ok with doing this change, but I would like to better understand whether I'm doing something wrong, and why making this change solved the problem.
Thanks!
Activity
sanex3339 commentedon Oct 27, 2020
Hmm. Obfuscated code looks like that:
So it renames the imported module identifiers.
Have to think about how to avoid this.
sanex3339 commentedon Oct 27, 2020
So, the idea is to convert all exports
to the
view.
After identifiers rename this construction becomes
Added `ExportSpecifierTransformer`. Fixed #791
sanex3339 commentedon Oct 27, 2020
PR: #792
Can you try it?
sanex3339 commentedon Oct 28, 2020
Merged into
master. Please try it frommasterbranch.I'll release this fix later today.
sanex3339 commentedon Oct 28, 2020
Released as
2.6.3. Please try it.rafaeleyng commentedon Nov 9, 2020
Sorry for the delay, somehow I messed up my notification settings and didn't see this earlier.
I've tested the latest
2.8.0and it works perfectly (I've reverted my code to the original and worked both with the new and old). Thanks for the quick response!