Unnecessary when eval-ing CoffeeScript about node-source-map-support HOT 2 CLOSED

That's a good point, and is something I should mention in the readme. I was using CoffeeScriptRedux to demonstrate this library and not to demonstrate an actual use case. You bring up a good use case for this library in run.coffee from the CoffeeScriptRedux source:

# NodeJS / V8 have no support for transforming positions in stack traces using
# sourceMap, so we must monkey-patch Error to display CoffeeScript source
# positions.

# Ideally, this would happen in a way that is scalable to multiple compile-to-
# JS languages trying to do the same thing in the same NodeJS process. We can
# implement it as if there were an API, and then patch in support for that
# API. The following maybe should be in its own npm module that multiple
# compilers can include.

This library allows multiple compile-to-JS languages with source maps to coexist in the same node process. I'll admit that it's probably not that strong a use case but it's nice to have when you need it :)

from node-source-map-support.

I can't take credit for that code, that was a contribution from @kevinmehall, who I'm sure would be really interested in this project.

Thanks for mentioning --eval in the readme.

This library allows multiple compile-to-JS languages with source maps to coexist in the same node process.

It'd probably also be good to explicitly mention this. I'd say that's a noteworthy benefit.

from node-source-map-support.