-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for CoffeeScript v2 #234
Comments
No such plans, sorry. We do not develop mincer anymore. Only do critical bugfixes. I can grant permissions to anyone who is able to maintain this project. As far as i understand you can split-out CS wrapper as plugin and be independent on my opinion/plans. May be someone already did it in npm. |
Hi @puzrin! Although I don't have time to properly maintain the project, I could make the necessary changes to support newer versions of coffeescript from now on. If you're interested please give me the permissions and I'll create a pull request. |
You don't need any special permissions to create PR. If it will be backward-compatible, i see no problems to accept it. |
I was updating a really old application to remove some vulnerable dependencies and wanted to update to coffeescript@2. I did the following and it ended up working pretty well: const mincer = require('mincer');
mincer.Template.libs.coffee = require('coffeescript'); |
Any plans to update the module to use "coffeescript" instead of "coffee-script"? Seems the new v2 is available only as "coffeescript".
The text was updated successfully, but these errors were encountered: