Coffee support #15
Open
Coffee support #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Tim,
As promised a patch bringing coffee script support for spark. There are two parts:
When coffee-script is required it patches 'require' to look for .coffee files as well. When no coffee-script is available we ignore it silently.
Second part is trivial: when coffee-script is available check if {app,server}.coffee is available in addition to it's .js counterpart and require it via node built-in (and extended by coffee-script) mechanism.
BTW: standardizing on a single entry point (either one is good, app.{js,coffee} is my preferred one) may be a good idea.
Ł.