Coffee-script as a Dependency
What a coincidence! I started to take part in a project which makes use of Set and they need to use this kind of approach:
//This makes coffeescript modules work (needed by indie-set) var coffee = require('coffee-script/register');
Is this really necessary? In my opinion it's adding some unneeded overhead.
If I'm correct, Coffee-Script should not be a Dependency but a dev-dependency of the project because it should be only necessary for coding, not for running. I understand Coffeescript like C code and JS as binary code: A compiler is needed only for development, but you can run the program without it.
In order to remove Coffeescript from the dependencies... I made (started, better said) a project in CoffeeScript in the past it was prepared to run in JS and CS but the NPM module was created only with JS code. A similar approach could leave CS out of the dependencies and make users who only need to run the program have less libraries to load.
This is what I made, it can be useful: https://gitlab.com/ekaitz-zarraga/cappuccino
Am I missing something?
All the best my friends.