-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Convert to ES Module format #76
Comments
How do you support conditional imports with es6 modules?
Hrm, this sounds interesting: what are you planning? :) |
No concrete plans. Just trying to get some interesting libraries in a more easily consumable format. Tooling for ES6 modules is a lot easier than CJS modules. |
I don't think we'll do this until node adds support for the |
I had a look at this today using rollup. e.g. I'm not sure how to have a DefinePlugin-like thing that causes different imports for node vs browser. |
Webpack 4.0 is getting proper ES6 support; so that might make this finally possible. |
not sure if it fits here - but will this allow letting babel transpile this module into ES5 too? |
fengari can already be transpiled. Infact fengari-web is distributed in ES5 form.
How old? lack of |
What do you think about porting the source to ES6 module format? It would be pretty easy to still publish to npm or other places as CJS in a build step. You could even include the ES6 code in the npm package for consumers who prefer that.
My personal desire is to make it easier to consume using rollup and only include functions my code uses.
The text was updated successfully, but these errors were encountered: