Comments on: Using CoffeeScript in Rails and even on Heroku

By: Co nowego w świecie Ruby’ego #2

Co nowego w świecie Ruby’ego #2 — Wed, 21 Jul 2010 20:03:25 +0000

[...] okazja. Gem bistro_car ułatwia organizację skryptów w aplikacji Railsowej, a Dr Nic napisał świetny tutorial wprowadzający do tego [...]

By: Sam

Sam — Mon, 28 Jun 2010 17:09:39 +0000

Is there a way to go from Javascript to CoffeeScript so I can convert my current JavaScript code and standardize on CoffeeScript?

Awesome write up!

By: moda

moda — Thu, 20 May 2010 20:15:09 +0000

Thanks for the great writeup, Dr. Nic.

By: Jeremy Ashkenas

Jeremy Ashkenas — Sat, 15 May 2010 14:35:03 +0000

One more update for folks who find this blog post via Google… As of CoffeeScript 0.6.2, using the `coffee` command to compile will now preserve directory structure.

coffee -wc -o public/javascripts app/coffee

Will now walk the `app/coffee` directory, and compile CoffeeScripts that it finds into the corresponding location in `public/javascripts`.

By: Don

Don — Tue, 27 Apr 2010 22:57:38 +0000

@will – because coffeescript does compile directly to JavaScript before use, and it’s not hidden, I think it can be safely used in an environment where there is pre-existing JavaScript.

If you decide to give up on coffeescript, you just throw the *.coffee files away and you keep the clean, generated JavaScript files.

Alternately, you can piece-meal convert your JavaScript files to CoffeeScript as you get to them.

It should definitely help ppl engage with JavaScript. Especially when JavaScript is now more prevalent on the server side and it should be possible to “try a chunk of JavaScript” without having to set up a dummy HTML page, etc.

By: Daniel

Daniel — Tue, 27 Apr 2010 11:56:15 +0000

Thanks for the great writeup, Dr. Nic.

If you like, using CoffeeScript with any web framework needn’t be complicated. The “coffee” command comes with a “–watch” option, which will rebuild your JavaScript files every time the source CoffeeScript is saved. So, running something like this:

coffee –wc -o public/javascripts app/coffee/**/*.coffee

Would be a fine way to keep your JS up to date as you develop. From there you can include it normally with the asset packager of your choice. No plugins or Heroku hacks required.

By: Tony

Tony — Tue, 27 Apr 2010 06:15:39 +0000

@Jeremy – for coffee 0.5.5 what worked for me was:

coffee app/scripts/*.coffee -wc -o public/javascripts

It seems the options must come last.

By: Jeff

Jeff — Tue, 27 Apr 2010 03:46:34 +0000

This is wonderful. I’ve been using haml + sass, now I can use coffeescripts for my Javascript need. I’m familiar with Javascript but it’ll be interesting to see where coffeescripts can lead me to.

Thank you for the nice writeup!

By: CoffeeScript, bistro_car, homebrew, and passenger gotcha « Jordan Brock

CoffeeScript, bistro_car, homebrew, and passenger gotcha « Jordan Brock — Thu, 08 Apr 2010 09:15:42 +0000

[...] I ran into a slight problem when following Dr Nic’s setup tutorial today. CoffeeScript worked, bistro_car worked within the console, but it didn’t work when [...]

By: Dr Nic

Dr Nic — Sun, 21 Mar 2010 03:47:38 +0000

@wynn – I think rack-coffee still requires `coffee` command to exist on the server (which it doesn’t on heroku)?