-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
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
Re-rexporting a module compiled to export.default = ...
#2117
Comments
That code is output from babel? What's the input? What babel version? |
The first code snippet is the Babel output. The code that I linked to here is the input. The babel version is the latest, I just did a fresh |
Ok, and how are you running babel? |
This is an Ember CLI app, so it's being run through the |
That's a lot of layers. It's going to be hard to do anything about it here without a reproduction with just babel. There may be an issue in one of those wrappers. |
Alright, no problem. I'll look into making a repo to isolate the issue. |
Awesome, thank you. That should help narrow down where the problem lies. |
Sounds like something somewhere is blacklisting the |
Alright, so I tried to reproduce with just Babel and was unable to, it all seems to work correctly. This prompted me to read more about |
Yeah, without a reproduction with just babel it's not actionable here. If you think the custom module formatter in the other project is the culprit, raising it over there sounds like the way to go. |
Alright, well thanks for the help! |
this is an issue with esperanto, pending a PR merge: esperantojs/esperanto#176 (which i forgot to do last night) |
I've been doing some IE debugging and noticed a show-stopper that seems to fall into Babel's territory. I keep getting the following issue:
Which traces back to the following code:
I went and looked up the
ember-wormhole
code that corresponds to this module, and it can be found here. In case you don't feel like following the link, it's just re-exporting another module.Is this an issue on Babel's end? To me, it seems like the problem is that Babel translates the re-export to
instead of
I looked around at all the other modules and they all seem to use the
exports['default']
syntax. It's only an issue with IE, and all the other modules seem to be OK.The text was updated successfully, but these errors were encountered: