Btw, off topic, but just a heads up that on my local machine (Mac) after a local npm i, none of the server-based tests worked in Firefox, and on Chrome the test at http://127.0.0.1:1337/ (running node server.js within /header-test) failed and caused the server script to exit with the following error:

fs.js:114
    throw err;
    ^

Error: ENOENT: no such file or directory, open 'script.map'
    at Object.openSync (fs.js:443:3)
    at Object.readFileSync (fs.js:343:35)
    at Server.<anonymous> (/Users/brett/node-source-map-support/header-test/server.js:27:18)
    at Server.emit (events.js:198:13)
    at parserOnIncoming (_http_server.js:677:12)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:109:17)

@brettz9 What is the status of this?

I'm not a maintainer here, @eyexpo-thomas . @evanw ?

Any chance this feature is still being worked on? Looks like this will help a handful of people with source map issues in nyc (istanbuljs/nyc#619)

@LinusU this is a small & useful feature for supporting nyc.

It's related to istanbuljs/nyc#619 (comment)

Currently i fix the stacktraces with source maps on nyc by editing my test suite.

With this feature merged & released instead I could do

nyc -a -r html -- node --require source-map-support/register-hook-require test/index.js

Which means the code coverage tooling can have working stacktraces / source maps without editing the source code of my test suite.

@evanw any movement on reviewing/merging this?

Sorry for the delay on this, released as 0.5.21

@brettz9 would you be able to submit a follow up PR that adds documentation for this to the readme? ❤️

@LinusU : I'm afraid I am not doing well health-wise these days, and this isn't fresh in my memory (and probably more submitted originally just to overcome a road block). Maybe you could ask on #239 ?

@brettz9 no worries, wish you all the best, take care of yourself!