Joined November 2013
·

matan

Israel
·
·

Mmmm thanks, much appreciated :)
So then the advice for using -r should be taken with a grain of salt shouldn't it? I didn't notice I was working with an old version until I checked now. WIth the latest CoffeeScript 1.6.3 stack traces are a bit more verbose, but are still clean of any CoffeeScript line references.... only pure javascript ones. So I'm not entirely sure what you meant in 'may no longer be as necessary as before` there......

This sounds useful. However since it needs to be the very first require, it can't be a conditional inside my code after already checking for the env value, which I use nconf for. And then, -rcoffee-trace isn't recognized by coffeescript (using coffeescript 1.4.0). I think you meant coffee -r ./node_modules/coffee-trace in a typical installation, and certainly not -rcoffeescript as one word. But even when using the later to run my app, it doesn't work.

Works for the sample you provide, but not for other exceptions. They show very uncaffeinated. E.g. I get stuff like:

Error: listen EACCES
    at errnoException (net.js:901:11)
    at Server._listen2 (net.js:1020:19)
    at listen (net.js:1061:10)
    at Server.listen (net.js:1127:5)
    at Object.<anonymous> (/home/matan/ingi/repos/front-end/app.coffee:100:10)
    at Object.<anonymous> (/home/matan/ingi/repos/front-end/app.coffee:112:4)
    at Module._compile (module.js:456:26)
    at Object.exports.run (/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:83:25)
    at compileScript (/usr/lib/coffee-script/lib/coffee-script/command.js:177:29)
    at /usr/lib/coffee-script/lib/coffee-script/command.js:152:18

Maybe it's related to coffee-trace's async initialization and instrumentation?

Well, it's sometimes easier to get it on board along with just installing sbt, if you're okay with running through sbt. Just pointing out an alternative.

I came here courtesy of google, looking for what pimping means in the Scalasphere, thanks! Well, with power comes some responsibility..... but isn't there a syntactically simpler way to add behavior to a type? this is soooo cumbersome and blingYoString is a name you'd never use in your code again, so it feels like it should have rather been anonymous. What do you think?

Achievements
56 Karma
0 Total ProTip Views