mirror of https://github.com/meteor/meteor.git synced 2026-05-02 03:01:46 -04:00

Files

David Glasser ea45e6a9f1 Allow plugins to register specific filenames

This is in addition to registering for extensions. Note that only the
new SourceProcessor APIs allow this, not registerSourceHandler.

The filename in question is the basename of the file.  The file can be
found in any directory in any package.  If you want to be more picky,
you can just ignore other ones in your processFilesForTarget.

This introduces the SourceProcessorSet abstraction, which simplifies a
lot of repeated code around matching filenames with processors and
avoiding duplicates.

Missing tests.

See also #3985.

2015-07-08 17:23:31 -07:00

.npm/plugin/compileCoffeescript

cache coffeescript compilation in memory

2015-06-04 11:17:19 -07:00

plugin

Allow plugins to register specific filenames

2015-07-08 17:23:31 -07:00

tests

Add a literate handler in the coffeescript package

2013-09-12 14:29:50 -07:00

.gitignore

More gitignore files.

2013-05-13 18:16:14 -07:00

bare_test_setup.coffee

Add test for #1668

2013-12-19 17:00:38 -08:00

bare_tests.js

Add test for #1668

2013-12-19 17:00:38 -08:00

coffeescript_test_setup.js

Implement package-level shared variables for CoffeeScript.

2013-06-18 09:59:42 -07:00

coffeescript_tests.js

Renamed Deps to Tracker in all packages

2014-08-27 20:05:22 -07:00

package.js

cache coffeescript compilation in memory

2015-06-04 11:17:19 -07:00

README.md

Clarify coffeescript README

2015-04-14 14:47:16 -07:00

README.md

coffeescript

CoffeeScript is a little language that compiles into JavaScript. It provides a simple syntax without lots of braces and parentheses. The code compiles one-to-one into the equivalent JS, and there is no interpretation at runtime.

CoffeeScript is supported on both the client and the server. Files ending with .coffee, .litcoffee, or .coffee.md are automatically compiled to JavaScript.

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 .coffee file 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 .js and .coffee files).
Package-scope variables declared in .js files are visible in any .coffee files in the same app or project.
There is no way to make a package-scope variable from a .coffee file 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 .js file that declares all of your package-scope variables. They can then be read, mutated, and extended in .coffee files.
If you want to share variables between .coffee files in the same package, and don't want to separately declare them in a .js file, we have an experimental feature that you may like. An object called share is visible in CoffeeScript code and is shared across all .coffee files in the same package. So, you can write share.foo for a value that is shared between all CoffeeScript code in a package, but doesn't escape that package.

Heavy CoffeeScript users, please let us know how this arrangement works for you, whether share is helpful for you, and anything else you'd like to see changed.