require, dependency management, load paths and all that jazz about coffeescript HOT 2 CLOSED

I'd rather not build in require() functionality -- it's outside the scope of the core language. It shouldn't be hard to have scripts interact. In Narwhal, or any CommonJS environment, use require() and the exports object, as you would in any other JS package.

In the browser, you should explicitly add the objects that you want to export to "window", or even "this" at the top-level (which is also "window"). ie:

window.square: x => x * x
window.cube:   x => square(x) * x

There are no globals by accident in CoffeeScript, but you can definitely add as many as you'd like on purpose. Closing the issue...

from coffeescript.

Jazz, you might want to take a look at my beans-server (which now servers coffee script too): http://github.com/weepy/bean-server

It builds dependencies by hiding them inside comments. So in coffee script it works like :

#= require 
#= require "local_file"

from coffeescript.