-
Notifications
You must be signed in to change notification settings - Fork 205
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
Plugin compatibility, exit vs enter? #84
Comments
Hey @yggie. No particular reasons. I believe changing it to |
hey @tleunen, I have written a simple plugin that inlines the JSON file imports as part of the babel compilation process (the repo is here). In one of my projects, I decided to use this plugin together with yours to get JSON files from a directory under an alias, something like: import json from 'custom-path/to/json' right now, this approach fails because my plugin uses |
Hmm... I see your point. |
Yes I have tried patching your library to use If it is generally accepted to use |
I must say I don't really see the reasons to use one versus the other. I can see the benefits of using |
I had trouble composing another module transformation babel plugin I wrote with this module, and I finally boiled it down to the fact that I was using
enter
and you were usingexit
(see here).Its really more of a question than an issue, was there any particular reason to use
exit
rather thanenter
for your code? Since this is a relatively simple transformation, would it make sense to perform it as early as possible so that it is easier to compose? Forgive me if this is a silly question, I have very little experience with babel myself.The text was updated successfully, but these errors were encountered: