Source code of released version | Source code of development version
CoffeeScript is supported on both the client and the server. Files
.coffee.md are automatically
Namespacing and CoffeeScript
Here's how CoffeeScript works with Meteor's namespacing.
Per the usual CoffeeScript convention, CoffeeScript variables are file-scoped by default (visible only in the
.coffeefile where they are defined.)
When writing a package, CoffeeScript-defined variables can be exported like any other variable (see Writing Packages). Exporting a variable pulls it up to package scope, meaning that it will be visible to all of the code in your app or package (both
Package-scope variables declared in
.jsfiles are visible in any
.coffeefiles in the same app or project.
There is no way to make a package-scope variable from a
.coffeefile other than exporting it. We couldn't figure out a way to make this fit naturally inside the CoffeeScript language. If you want to use package-scope variables with CoffeeScript, one way is to make a short
.jsfile that declares all of your package-scope variables. They can then be read, mutated, and extended in
If you want to share variables between
.coffeefiles in the same package, and don't want to separately declare them in a
.jsfile, we have an experimental feature that you may like. An object called
shareis visible in CoffeeScript code and is shared across all
.coffeefiles in the same package. So, you can write
share.foofor a value that is shared between all CoffeeScript code in a package, but doesn't escape that package.
Modules and CoffeeScript
See Modules » CoffeeScript Syntax.
Testing This Package
Follow the instructions
to check out the Meteor repo and run
Once you can do that successfully, to test the
coffeescript package run:
./meteor test-packages packages/non-core/coffeescript