node-source-map-support
node-source-map-support copied to clipboard
evanw
Adds source map support to node.js (for stack traces)
When in development, we don't generate sourcemaps and use babel-register to dynamically transpile the source code. I noticed that if we load `require('source-map-support').install();` in that context, the error stack shows...
I am attempting to use source-map-support with a platform where v8 is embedded directly into an application, which is not Node or a browser ([it's a plugin for the Unreal...
`node v8.0.0` src/throw-err.js (not compiled) ```javascript import 'source-map-support/register' const main = async () => { throw new Error('wooot') } main().catch(console.error) ``` lib/throw-err.js (compiled with babel) ```javascript 'use strict'; require('source-map-support/register'); function...
Could you please add support for loading gzip-compressed source maps? It'd be useful e.g. for projects packaged using [pkg](https://github.com/zeit/pkg).
It would be handy if this project published a changelog and tagged releases so I can easily see what has changed and upgrade to new versions.
Chrome 66's dev tools changed its handling of windows file paths. It now seems to interpret windows file paths properly so that relative paths work properly. It is no longer...
This covers the use cases that b40cc25 doesn't; namely, if several libraries reference different versions of source-map-support, then they would previously all get their own source map caches, handler arrays,...
http-server 0.8.5 seems to be throwing this error in some cases `The header content contains invalid characters`
Webpack and Browserify both automatically check for a `browser` property in `package.json` when resolving external module paths: https://webpack.js.org/configuration/resolve/#resolve-mainfields https://github.com/browserify/browserify-handbook#browser-field This PR ensures that the correct version will be used when...
