-
Notifications
You must be signed in to change notification settings - Fork 459
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
Does not work with babel-register and babel-polyfill #89
Comments
I believe it's a poor choice to go with async-to-gen, as it does not play nice with other extensions. I contacted the author and suggested to become part of the babel solution: Please make micro so it plays well with babel! async-to-gen does not have to become part of your build distribution, so something like the previous -no-babel should be made into --no-transform (or something that makes more sense), not doing any transforms on the fly. And why remove the babel dependency if most of the javascript programmers use it? |
Maybe when Node.js 7.0 is out, which won't be too long, this problem could be solved. |
@amio Seems like Lee Byron worked on a solution in async-to-gen: leebyron/async-to-gen#15 (comment) |
Cool, thanks @timneutkens |
@amio @Morriz #114 was just merged which checks for async before executing async-to-gen's register. This will allow you to use node 7 with |
Apologies if this is a dumb question, but I am still unclear how to use Micro with babel. Any tips on setting it up? I have tried several solutions and nothing seems to work. Thanks in advance! |
@zachariahtimothy I got micro working with babel with these scripts in the package.json Below the settings, I used to deploy via now
|
If I do a
node -r babel-register -r babel-polyfill node_modules/.bin/micro -p 3000 src/index.js
I still get errors about import/export statements:
And yes, transpiling works (with preset-node6):
babel src --out-dir build
Any idea what might cause this?
The text was updated successfully, but these errors were encountered: