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:
- At 39k gzipped (compare to jQuery at 29k),
coffee-script.jsis a big file; so unless you're actually letting your users run their own CoffeeScript, you really shouldn't use it in production. - As mentioned in the documentation, each CoffeeScript snippet will be in its own anonymous closure. So your example snippet wouldn't do anything—
squareswouldn't be visible outside of the script. Instead, you'd want to change it towindow.squares = .... - All CoffeeScript code, whether external or inline, will run after all JavaScript code on the page. That's because
coffee-script.jsdoesn't read your<script type="text/coffeescript>tags until after the document is ready, by which time your JavaScripts have already run. - 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 doingXMLHTTPRequests onfile://paths.) - 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.
Perhaps you're looking for this?
"text/coffeescript"Script TagsWhile it’s not recommended for serious use, CoffeeScripts may be included directly within the browser using
<script type="text/coffeescript">tags. The source includes a compressed and minified version of the compiler (Download current version here, 77k when gzipped) asdocs/v2/browser-compiler-legacy/coffeescript.js. Include this file on a page with inline CoffeeScript tags, and it will compile and evaluate them in order.The usual caveats about CoffeeScript apply — your inline scripts will run within a closure wrapper, so if you want to expose global variables or functions, attach them to the
windowobject.
<script crossorigin src="https://coffeescript.org/v2/browser-compiler-legacy/coffeescript.js"></script>
<script type="text/coffeescript">
square = (x) -> x * x
list = [1, 2, 3, 4, 5]
squares = (square num for num in list)
console.log squares
</script>The answer is yes. I won't repeat @Trevor's excellent answer, but rather just provide an example of what you're thinking about:
http://forgivingworm.wordpress.com/2010/09/27/running-coffeescript-in-browser/
Basically you
- Tag your coffeescript with the text/coffeescript
- Include coffee-script.js after all coffeescript on the page (the compiler will evaluate and compile all coffeescript in order)
Sample HTML below
<html>
<head>
<title>In-Browser test</title>
<script type=”text/javascript” src=”http://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js”> </script>
<script type=”text/coffeescript”>
$ -> $(‘#header‘).css ‘background-color‘, ‘green‘
</script>
<script type=”text/javascript” src=”http://github.com/jashkenas/coffee-script/raw/master/extras/coffee-script.js”> </script>
</head>
<body>
<h1 id=”header” style=”color:white”>CoffeeScript is alive!</h1>
</body>
</html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8"/>
<title>CoffeScript on browser</title>
</head>
<body>
<script type="text/coffeescript">
alert 'It works!'
</script>
<script src="http://cdnjs.cloudflare.com/ajax/libs/coffee-script/1.7.1/coffee-script.min.js"></script>
</body>
</html>
- CoffeeScript has to be loaded after the script you want to run.
- if using
srcyou must be able to access the file viaXMLHTTPRequest, in particular it fails on browsers withfile://.