-
Notifications
You must be signed in to change notification settings - Fork 20
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
Adopt a more generic approach? #9
Comments
What does |
The idea is to deliver different binaries for different versions of Node.js, within the same package. Personally, I don’t have a need for it. It could probably be omitted in a first version of a standard and be added later, should it become necessary. |
I like the idea of starting with browser bundles. Then |
I think it is the right direction, but we should adopt a more granular/modular approach. ES2015 may indeed be transpiled to ES5, except for Proxies. Same goes for other modern features for a target ES3 runtime. So I'm thinking of something like autoprefixer, plus a way to alert the user that a given source feature to destination runtime transformation is impossible (i.e. an error message like |
Maybe related to jsforum/jsforum#5? 🤔 |
I’d love to have something like this:
An additional entry (similar to
"main"
) could be"files"
, which would work like"browser"
.Use cases:
The text was updated successfully, but these errors were encountered: