AriaMinaei / pretty-error

See node.js errors with less clutter
MIT License
1.52k stars 49 forks source link

CoffeeScript support #2

Closed ELLIOTTCABLE closed 8 years ago

ELLIOTTCABLE commented 10 years ago

At the moment, CoffeeScript syntax errors get mildly mangled:

  Error: unexpected newline

  - /Users/ELLIOTTCABLE/Dropbox/Code/Paws/Paws.js/Source/additional.coffee:15:71: er
    ror: unexpected newline

  - @tput new (require('blessed').Tput) term: process.env['TERM']

  -                                                                       ^
    0m

It's not a huge deal, but it's mildly annoying to disable pretty-error if I need more information about a syntax error.

AriaMinaei commented 10 years ago

Yeah, this is annoying.

It's mainly because RenderKid tries to be smart when dealing with leading whitespace, but that's not needed in this specific case.

I'll have to think of something, but could you post a screenshot of your console with the mangled syntax error? I have to compare it with mine, as I'm not sure if whitespace management is the only problem here. That 0m in the last line is not supposed to be there.

image

ELLIOTTCABLE commented 10 years ago

Ugh, I don't even remember what the exact code causing the error was; I regret not recording where I was before submitting this. /=

AriaMinaei commented 10 years ago

That's okay. This is probably gonna take some time, since I have to add a few features to RenderKid. But if this bug is annoying you too much, I'll work on it sooner, so, please let me know :)

ELLIOTTCABLE commented 10 years ago

@AriaMinaei definitely back-burner stuff! (=

AriaMinaei commented 10 years ago

Okay then :)

alexgorbatchev commented 10 years ago

CoffeeScript support is always awesome :) especially when the module itself is in CS :100:

ELLIOTTCABLE commented 8 years ago

Cool! If I ever run into weird stack-trace errors with CoffeeScript again, I'll come back here with more details. <3

I'm sorry I failed as a feedback-contributor! >':

AriaMinaei commented 8 years ago

@ELLIOTTCABLE: not at all :) I was supposed to fix this issue a long time ago.