Error with latest Node: Arguments to path.resolve must be strings Use --force to continue.
cgross opened this issue · 4 comments
Looks like there was some change to Path.
Only occurs when options.base is undefined.
TypeError: Arguments to path.resolve must be strings
at Object.exports.resolve (path.js:313:15)
at Object.exports.relative (path.js:370:20)
at /home/bpippin/Texeltek/ircop-ui/node_modules/grunt-angular-templates/tasks/lib/compiler.js:17:54
at /home/bpippin/Texeltek/ircop-ui/node_modules/grunt/node_modules/async/lib/async.js:541:13
at iterate (/home/bpippin/Texeltek/ircop-ui/node_modules/grunt/node_modules/async/lib/async.js:108:13)
at async.forEachSeries (/home/bpippin/Texeltek/ircop-ui/node_modules/grunt/node_modules/async/lib/async.js:124:9)
at _concat (/home/bpippin/Texeltek/ircop-ui/node_modules/grunt/node_modules/async/lib/async.js:540:9)
at Object.concatSeries (/home/bpippin/Texeltek/ircop-ui/node_modules/grunt/node_modules/async/lib/async.js:174:23)
at concat (/home/bpippin/Texeltek/ircop-ui/node_modules/grunt-angular-templates/tasks/lib/compiler.js:16:22)
at Object.compile (/home/bpippin/Texeltek/ircop-ui/node_modules/grunt-angular-templates/tasks/lib/compiler.js:29:5)
Well, crap. I'll take care of it :) Thanks for letting me know! I guess I haven't npm install
ed in a while...
Yea me neither :) Someone else was setting up a new laptop and noticed it.
had same problem today - downgraded to 0.3.0 - works fine
Ah, I found the issue. It was related to some refactoring in PR #16, I believe, which should be very simple to fix!