Closed ghost closed 3 years ago
For info: Removing isPath:true fixed this issue
So is this the legitimate answer? Should we change path.dirname(grunt.file.expand(f))
to handle an array as well as a string?
Pull requests #44 and #45 are both meant to fix this. As for whether removing isPath: true
is a good workaround, the README says this option "is usually necessary when passing the values to another grunt task like concat
or uglify
", but I haven't verified it.
We've fixed this in 4.0 :)
Updated to node v6.9.2 and now get the following error in a yo generator that includes a Gruntfile.js
I've made no changes to the Gruntfile.js and this is the config of dom_munger read object:
Any suggestions?