Feature request: Support for ES6 compiling

watzon commented 9 years ago

It would be really nice if we could just compile the .es6.js extension to ES5

fujiwaraficc commented 9 years ago

+1

calvinjuarez commented 9 years ago

I was just thinking this the other day. Transpiling would be a killer feature right now.

Babel may be helpful. https://babeljs.io

Andreyco commented 9 years ago

Similar to #554

watzon commented 9 years ago

+1 please devs!

marioluevanos commented 8 years ago

+1

fmaida commented 8 years ago

Another +1

bdkjones commented 8 years ago

Hey guys. I'm not ignoring you.

Here's the top-secret info: there's a build of CodeKit with Babel built in and working perfectly. (Among many other popular requests on this GitHub page.) It's not ready for public release yet, but I'm getting close to a closed alpha test, followed by a closed beta, followed by blowing people's minds.

Hang in there. I'll ask for testers on Twitter in probably a month or so.

yougotashovel commented 8 years ago

@bdkjones Any updates on the update?

Andreyco commented 8 years ago

Do we really want CK to do this? In the end, what are you trying to achieve? With all the respect to CK, isn't out there tool better thank CK to achieve same results? Are you writing app in React? If so, pick Webpack (or Browserify), get yourself hot transformation (hot loading) and use CK for other stuff which it handles just great... Once again, love CK, awesome job here! :)

redler commented 8 years ago

If you're going to go that road, it might make better sense to use something like gulp. I think there are a bunch of nice use cases for Babel support in CK. If you've got a longstanding CK workflow (let's say with less, jshint, and uglify), and you just want to dip your toe into React by folding in a few components, it would be awfully nice to have have your React/jsx code drop right into that same workflow (linted, ES6 transformed, jsx transformed, then all uglified -- along with your regular JS stuff). Likewise, even without React you might want to start adding ES6isms to your JS; if the CK pipeline could pass your JS through Babel, it would make it very easy to jump in with ES6 at your leisure.

theskillwithin commented 8 years ago

Plz add this https://babeljs.io/

t0t commented 8 years ago

I would like it too...

adampatterson commented 8 years ago

@bdkjones if you are still looking for testers I would be happy to help. I have 40+ sites with day to day maintenance as well as a handful of React projects in the mix. Gulp/Grunt are driving me insane!

bdkjones commented 8 years ago

Soon.

On 29Feb 2016, at 08:44, Adam Patterson notifications@github.com wrote:

@bdkjones https://github.com/bdkjones if you are still looking for testers I would be happy to help. I have 40+ sites with day to day maintenance as well as a handful of React projects in the mix. Gulp/Grunt are driving me insane!

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/562#issuecomment-190282887.

grosewarne commented 8 years ago

+1! Yes please! I need it for the latest foundation´s version 6.2.0 https://github.com/zurb/foundation-sites/wiki/Upgrading-to-Foundation-6.2

The JavaScript is now written in ES2015, which means if you consume the js/ folder of the Foundation package as part of a build process, it will need to be transpiled using Babel.

tconroy commented 8 years ago

👍 !!

jlmakes commented 8 years ago

The modern JavaScript workflow with CLI task runners is wonderful for advanced and expert developers, but I think CodeKit supporting ES6 transpiling would be an excellent way to help beginners and intermediate developers start using the future of JavaScript.

💯