Skip to content
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 with latest Node: Arguments to path.resolve must be strings Use --force to continue. #19

Closed
cgross opened this issue Apr 18, 2013 · 4 comments

Comments

@cgross
Copy link

cgross commented Apr 18, 2013

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)

@ericclemmons
Copy link
Owner

Well, crap. I'll take care of it :) Thanks for letting me know! I guess I haven't npm installed in a while...

@cgross
Copy link
Author

cgross commented Apr 19, 2013

Yea me neither :) Someone else was setting up a new laptop and noticed it.

@4vanger
Copy link

4vanger commented Apr 20, 2013

had same problem today - downgraded to 0.3.0 - works fine

@ericclemmons
Copy link
Owner

Ah, I found the issue. It was related to some refactoring in PR #16, I believe, which should be very simple to fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants