node-source-map-support
node-source-map-support copied to clipboard
evanw
Adds source map support to node.js (for stack traces)
Hello, I am facing below issue: WARNING in ./node_modules/typescript/lib/typescript.js Module not found: Error: Can't resolve 'crypto' in 'C:\Work\VBS Portal\FeatureCode\InsVerifyApp\InsVerifyApp\ClientApp\node_modules\typescript\lib' WARNING in ./node_modules/source-map-support/source-map-support.js Module not found: Error: Can't resolve 'fs' in...
Hey there! I'm pretty new to TypeScript/jest and I spent hours in figuring out why line numbering in failing tests are wrong so please bear with me. I'm not sure...
When using `cheap-module-eval-source-map` or equivalent in Webpack, the sourcemap is embbeded in the `eval()` statement generated by Webpack... thus, `source-map-support` cannot access the actual source and perform the mapping. ......
In `ts-node`, if someone modifies a `.ts` file, removes it from their `require.cache`, and then re-requires it, we will have a new sourcemap for that file. We need a way...
This bug was hard to track down! It breaks all my tests, and has been a real hinderance to my _[jest-preset-coffeescript](https://github.com/danielbayley/jest-preset-coffeescript/runs/1254200867?check_suite_focus=true)_ package. Fixes #254.
Hi I have a boilerplate express project in TS. My setup is that I run the project and the build tool chain inside a docker container; the goal being simple...
I am created react project by using npx create-react-app. I have installed jest package for unit test. when I was run unit test, this Cannot find module **'source-map' from 'source-map-support.js'**...
Hello, I suspect the library to generate a memory leak :/ After some research, I found this PR #215 that seems to be a good fix :) However, I doesn't...
When I source `browser-source-map-support.js` in Chrome 42, I get the following warning in the JS console: > Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects...
Shipping a 1.0 release will make it easier for different projects to end up with the same instance of `source-map-support` (by relying on dependency deduplication). This would lessen the impact...
