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

Problems in CoffeeScript scripts do not include the file name #331

Closed
joscha opened this Issue Sep 11, 2012 · 4 comments

Comments

Projects
None yet
3 participants
@joscha

joscha commented Sep 11, 2012

If there is a compilation problem in a CoffeeScript file, the bundler does not mention the file where it actually happens in, which makes debugging hard sometimes:

--- 8< ---
Your app is crashing. Here's the latest log.

Errors prevented startup:
Exception while bundling application:
Error: Parse error on line 58: Unexpected 'INDENT'
at Object.parseError (/usr/local/meteor/lib/node_modules/coffee-script/lib/coffee-script/parser.js:473:11)
at Object.parse (/usr/local/meteor/lib/node_modules/coffee-script/lib/coffee-script/parser.js:522:22)
at Object.compile (/usr/local/meteor/lib/node_modules/coffee-script/lib/coffee-script/coffee-script.js:43:20)
at /usr/local/meteor/packages/coffeescript/package.js:14:34
at [object Object].add_file (/usr/local/meteor/app/lib/bundler.js:196:5)
at /usr/local/meteor/app/lib/bundler.js:97:16
at Array.forEach (native)
at Function. (/usr/local/meteor/app/lib/third/underscore.js:76:11)
at /usr/local/meteor/app/lib/bundler.js:96:11
at Array.forEach (native)
Your application is crashing. Waiting for file change.

--- 8< ---

Including the file name where the parse error happened would be very much appreciated.

@tifroz

This comment has been minimized.

tifroz commented Sep 13, 2012

+1

@joscha

This comment has been minimized.

joscha commented Sep 24, 2012

Thanks! Works like a charm in 0.4.1 - now the only thing which could improve this even more is to add the actual line of the coffeescript source :-)

@glasser

This comment has been minimized.

Member

glasser commented Sep 24, 2012

Er, it doesn't? eg "Parse error on line 58" above?

@joscha

This comment has been minimized.

joscha commented Sep 24, 2012

Sorry for the confusion, my bad, I was looking at an exception that got thrown ...the parsing errors do contain the line #!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment