Don't put ES6 code in npm, for now

2Comments

Write your comment…

This comment has received 1 appreciation.

Therefore I use ES6 for development and push it on GitHub. And precompile this codebase with babel to ES5 code and publish it on npm – without the ES6 code. Additionally the pkg.main refers to the ES5 entry point :)

Jep of course. If you install a package w/ npm, you wanna start directly and don't wanna debug these packages too :P

Write a reply...

I just see the problem with import/export. Other parts work well for me. However, I think we should use native features only, what do not require transpiler.

However, people want ES6 or even ES7, and I want CoffeeScript and ClojureScript, there are lots of languages out there, and most people just hate ES5.

Write a reply...

Join a friendly and inclusive Q&A network for coders

  • 🖥Pick the technologies you like & read great content through your feed.
  • 💬Ask a question when you want to learn more about anything.
  • 🚀Share what you know & build your portfolio.
Sign up nowLearn more

loading ...