You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Please upgrade source-map to 0.7.2 to get speed improvements #206
@andreicristianpetcu @devsnek there is no case for async source map consumer other than problems of specific ill-thought implementation by Mozilla.
Like: await in stack trace handler? Are they nuts?
source-map@<0.7.1 has an invalid typings field in its package.json which is causing VS Code to report an error that it can't find the type declarations. This is fixed in source-map@>=0.7.1.
Has anyone done benchmarks of the various options? I haven't, so I really
don't know if they're different: if wasm is faster/slower/whatever.
EDIT: I see them in the README now. Will check them out.
Activity
LinusU commentedon Mar 4, 2018
This is awesome, we need to figure out what breaking changes (if any) occurred in 0.7.0, then we are good to go!
PRs welcome!
LinusU commentedon Mar 4, 2018
Hmmmm, this might be a big problem for us... 🤔
loganfsmyth commentedon Mar 4, 2018
Is this possible?
SourceMapConsumernow returns aPromise, but catching and mapping thrown exceptions needs to be synchronous.SimenB commentedon Mar 18, 2018
Jest is also unable to upgrade due to the lack of a sync API, FWIW
niieani commentedon Apr 28, 2018
@SimenB Could deasync help here? It hooks into Node's event loop and essentially makes any async operation a sync one.
devsnek commentedon Jun 20, 2019
I published https://www.npmjs.com/package/@snek/source-map-support which works nicely in node and may work in browsers that allow you to load reasonable sized wasms synchronously. It wraps the 0.8.0-beta.0 release of source-map.
pkit commentedon May 6, 2021
@andreicristianpetcu
@devsnek there is no case for async source map consumer other than problems of specific ill-thought implementation by Mozilla.
Like: await in stack trace handler? Are they nuts?
cspotcode commentedon Aug 30, 2021
@cspotcode/source-map-supportuses@cspotcode/source-map-consumerwhich is a fork ofsource-mapthat only has the consumer.@cspotcode/source-mapincludes the generator, too.These are based on the latest
source-mapversion. They use WASM and have a sync API.You might have luck giving them a try. It's all open-source, so of course the changes can be ported over.
jordanbtucker commentedon Feb 24, 2022
This will also fix an annoying issue in VS Code.
source-map@<0.7.1 has an invalid
typingsfield in itspackage.jsonwhich is causing VS Code to report an error that it can't find the type declarations. This is fixed in source-map@>=0.7.1.SimenB commentedon Apr 20, 2022
Babel has migrated to https://npmjs.com/package/@jridgewell/trace-mapping, should this module as well? Code change seems fairly trivial (no idea about browser support, but probably?)
cspotcode commentedon Apr 20, 2022
SimenB commentedon Apr 20, 2022
Jest and C8 (via
v8-to-istanbul) has also migrated, fwiwcspotcode commentedon Apr 20, 2022
I can migrate @cspotcode/source-map-support as well.
Would be nice to consolidate the ecosystem a bit more.