Created
June 6, 2012 14:05
-
-
Save StanAngeloff/2882059 to your computer and use it in GitHub Desktop.
CoffeeScript `include ..` extension
This file contains hidden or 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
| fs = require 'fs' | |
| path = require 'path' | |
| CoffeeScript = require 'coffee-script' | |
| CoffeeScript.on 'compile', (task) -> | |
| task.input = task.input.replace /^([ \t]*)#=\s*include\s+(.*)$/im, (group, indent, file) -> | |
| "#{indent}`#{ fs.readFileSync(path.join(path.dirname(task.file), file), 'utf8') }`" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I actually do keep around a very old branch that did
imports in a similar way (extended the grammar). I agree, AST manipulation is a more practical and bullet-proof approach, but at this compiler stage I'd need to re-parse the source twice (once in the extension and once in CS itself) and the LoC would likely explode.Looking forward to anything you could offer in CS2 in terms of extensibility, been keeping up with the Wiki and Twitter.
EDIT: OK, maybe not explode, but definitely grow somewhat. I guess a parse -> AST -> walk -> substitute -> return JS chain would be enough.