Closed matepek closed 6 years ago
Hey matepek,
I'm sorry, this was just a stupid bug. I'm trying to keep this package functional, but not investing a lot in it, given the decline of grunt.
I've got a fix published to npm at version 2.0.2.
thanks, Laban
Running grunt, I'm getting this:
The problem is pretty straightforward, but the fix isn't for me.
(I'm really newbie in the JS world.)
[I] ➜ node --version
v9.8.0 [I] ➜ grunt --version grunt-cli v1.2.0 grunt v1.0.2