Skip to content

Very useless error message #291

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

Open
adius opened this issue May 3, 2015 · 2 comments
Open

Very useless error message #291

adius opened this issue May 3, 2015 · 2 comments

Comments

@adius
Copy link

adius commented May 3, 2015

Error: Uncaught, unspecified "error" event.
    at Error (native)
    at emit (events.js:87:13)
    at TaskBase.run (/Users/adrian/Projects/fakesome/node_modules/jake/lib/task/task.js:268:14)
    at TaskBase.handlePrereqComplete (/Users/adrian/Projects/fakesome/node_modules/jake/lib/task/task.js:229:12)
    at null.<anonymous> (/Users/adrian/Projects/fakesome/node_modules/jake/lib/task/task.js:189:16)
    at g (events.js:199:16)
    at emit (events.js:104:17)
    at FileBase.complete (/Users/adrian/Projects/fakesome/node_modules/jake/lib/task/file_task.js:93:10)
    at TaskBase.run (/Users/adrian/Projects/fakesome/node_modules/jake/lib/task/task.js:277:12)
    at TaskBase.runPrereqs (/Users/adrian/Projects/fakesome/node_modules/jake/lib/task/task.js:159:12)
@mde
Copy link
Contributor

mde commented May 25, 2015

Could you provide a little bit more context? Your bug report doesn't provide much more info than the useless error message. :)

@hobberwickey
Copy link

I think I can provide some more context because I'm running into this too. Basically, if there's a syntax error in a file(s) and you try to run a jake task you just get an error like

SyntaxError: Unexpected token :
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:387:25)

Which really doesn't help you track anything down. Here's an example:

I have a jake task for launching my server

desc("Start server")
task("launch", function(){
jake.exec("nodemon server.js --watch src --watch server.js", {interactive: true}, function(){
complete();
})
})

If there's an error anywhere in my Jakefile I'll have to run the nodemon sever.js... command manually in order to get the location of the syntax error. So somewhere along the lines Jake's swallowing all the error context.

EDIT: Sorry for the crappy formatting

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