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

Proposal for es6 workflow #62

Closed
wants to merge 2 commits into from
Closed

Proposal for es6 workflow #62

wants to merge 2 commits into from

Conversation

stoeffel
Copy link
Contributor

Simple es6 workflow proposal

  • Authored files are in es6 folder.
  • npm run-script to5 compiles es6-files into the root of the project.
  • npm test first transpiles es6 files.

I implemented add.es6 as a sample.

Checkout babeljs.io for more infos on babel (former 6to5).
refs #42

@tjmehta tjmehta mentioned this pull request Feb 16, 2015
@tjmehta
Copy link
Owner

tjmehta commented Feb 25, 2015

I do sense ES6 becoming more mainstream day by day and I am very excited about it. However, I've decided to hold on this for now. I think it's important for modules to follow mainstream development patterns to reduce barriers to contribution. I realize that ES6 will soon become the standard, but I don't feel it is there quite yet. Specifically, I hesitate to use ES6 for module development while it remains behind a flag in node. If I were creating an application I would be completely willing to give ES6 a spin, just not for a module.

@tjmehta
Copy link
Owner

tjmehta commented Feb 25, 2015

Thanks for taking the time to show me the workflow. I am definitely excited to use this on my next side-project.

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

Successfully merging this pull request may close these issues.

2 participants