Is there a way to send CoffeeScript to the client’s browser and have it compiled to JavaScript *there*?

Jeremy already has this one, but let me add some important details and caveats:

  1. At 39k gzipped (compare to jQuery at 29k), coffee-script.js is a big file; so unless you’re actually letting your users run their own CoffeeScript, you really shouldn’t use it in production.
  2. As mentioned in the documentation, each CoffeeScript snippet will be in its own anonymous closure. So your example snippet wouldn’t do anything—squares wouldn’t be visible outside of the script. Instead, you’d want to change it to window.squares = ....
  3. All CoffeeScript code, whether external or inline, will run after all JavaScript code on the page. That’s because coffee-script.js doesn’t read your <script type="text/coffeescript> tags until after the document is ready, by which time your JavaScripts have already run.
  4. Remote CoffeeScripts are loaded via XMLHTTPRequest, which means that they must be hosted on the same domain as your site. (Certain browsers—Chrome, at least—also have a problem with doing XMLHTTPRequests on file:// paths.)
  5. Currently, the order in which different remote CoffeeScripts run is not guaranteed. I submitted a patch for this, but it’s not officially a part of CoffeeScript yet. See this pull request.

So, you might want to look at some alternatives for serving CoffeeScript as compiled JavaScript instead. If you’re developing for a Ruby or Python server, there are plugins available. I’ve tried to list them all at http://github.com/jashkenas/coffee-script/wiki/Web-framework-plugins.

If you’re developing a site without a backend, a tool I highly recommend looking at is Middleman, which lets you work with CoffeeScript (as well as Haml and Sass, if you want) during development, then compile and minify it for production deployment.

Leave a Comment