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
Error: Grunt attempted to load a .coffee file but CoffeeScript was not installed. #1725
Comments
should be fixed via https://github.com/gruntjs/grunt-cli/releases/tag/v1.4.1 |
@vladikoff just grabbed grunt-cli@1.4.1 and still getting the error. |
could you please try https://github.com/gruntjs/grunt-cli/releases/tag/v1.3.2 |
@vladikoff I managed to track it down to this Grunt plugin: https://github.com/berlysia/grunt-encode-asset-base64 The error occurs no matter what grunt-cli version I use, I tried 1.0.0 through 1.4.1 This is really weird as I was using grunt & grunt-cli with this plugin for several years without this error. The plugin is 6 years old! Is this something that can/should be fixed on the grunt side? Or is it on the plugin author to fix? |
Ah it occurs with grunt versions 1.2.0 and later, and this behavior was called out in the change notes. The plugin I linked uses both a js file and a coffee file... can grunt simply prioritize the js one to avoid the missing Coffee dependency issue? |
This reverts commit e820858.
* 1.4.1 * Revert "Revert liftoff changes due to gruntjs/grunt#1725 (#143)" This reverts commit e820858.
@derrickb i think migrating the plugin from coffeescript should fix it |
I've just come back to my project on a fresh Windows install after some months away from it. I've been using grunt with a Gruntfile.js for years without this issue.
I installed grunt-cli 1.4.0 and get this error when attempting to run grunt in my project:
I'm not using any CoffeeScript files, and do not want to add it as a dependency just to clear this error. I get the error for almost every task in my grunt file.
I tried running
npm i -f
as I saw that referenced elsewhere from a google search. I also updated local grunt to 1.3.0The text was updated successfully, but these errors were encountered: