Rehab helps you deal with your coffee dependency
You won't immediately realize you have a problem. Just a few .coffee files here and there and all you need is
coffee --join to make it work.
Then, one day, you realize you need more! You need your files to have order or it won't work properly. And that little friend transpiler won't help. You start making maneuvers, like huge Cakefiles, file lists(!) or even put your files in alphabetic order (!!!). But one day you stop and think "There should be a better way to do that! I need help!"
Yes, we know... That's why we are here.
Rehab deals with coffeescript dependency using a simple tag
#_require [filename] on the file that have dependencies.
#_require ../filenameA.coffee#_require ../filenameB.coffee
With that on your troublesome files and Rehab will give you a list of files in the right order so you can use it, for instance, with your Cakefile:
require 'child_process'Rehab = require 'rehab'task 'build''Build coffee2js using Rehab'= ->consolelog "Building project from src/*.coffee to lib/app.js"files = process './src'to_single_file = "--join lib/app.js"from_files = "--compile "exec "coffee "throw err if err
©2012 David Lojudice Sobrinho and available under the MIT license:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.