Skip to content
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

Support for es6 imports #15

Closed
kkwiatkowski opened this issue Aug 24, 2016 · 4 comments
Closed

Support for es6 imports #15

kkwiatkowski opened this issue Aug 24, 2016 · 4 comments

Comments

@kkwiatkowski
Copy link

It would be great to give ability to import your library as ES6 module (without transpilation) in projects written in ES6 (there is possiblity to import in such way with rollup).

Only one additional key in package.json is needed.

@coderitual
Copy link
Owner

Good point. I will add it!

@coderitual
Copy link
Owner

Are you sure only one package.json field is required? I assume that the whole project should not be transpiled. The tricky part is the feature heavily used in the library which is proposal only and might not be included anytime soon.

@kkwiatkowski
Copy link
Author

Right now it does not look so easy and I'm not sure about it anymore since project has evolved during that time.

I'm not even sure if exposing additional entry point with not transpiled ES6 modules would give any gain just because babel is dealing with it fine.
However if we think about native ES6 modules, it might be worth to introduce ES6 module compatible build with additional ES next entry in package.json file.

@coderitual
Copy link
Owner

Closing then, it looks like conceptual discussion rather than a matter of the improvement itself. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants