@contrast/synchronous-source-maps
Advanced tools
A synchronous version of the mozilla source-map library based on @snek/source-map-support
A synchronous version of the mozilla source-map library based on @snek/source-map-support
The Mozilla official source-map library moved to being asynchronous after its 0.60 release in order to support WASM source maps. However, the Node agent requires a sync interface because it uses source maps in the processing of stack traces.
@snek/source-map-support builds what we need, providing a sync interace, but it is wrapped in the source-map-support library when we want the underlying functionality. Moreover, it doesn't support filename translations, and we don't want to be dependent on a fork of the library without a source tree (it was never published to github and has less than 5 weekly downloads).
As such, this fork rips out the functionality from the sync port.
Sources of background info:
FAQs
A synchronous version of the mozilla source-map library based on @snek/source-map-support
The npm package @contrast/synchronous-source-maps receives a total of 5,473 weekly downloads. As such, @contrast/synchronous-source-maps popularity was classified as popular.
We found that @contrast/synchronous-source-maps demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 17 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In an open letter, JavaScript community leaders urge Oracle to give up the JavaScript trademark, arguing that it has been effectively abandoned through nonuse.
Security News
The initial version of the Socket Python SDK is now on PyPI, enabling developers to more easily interact with the Socket REST API in Python projects.
Security News
Floating dependency ranges in npm can introduce instability and security risks into your project by allowing unverified or incompatible versions to be installed automatically, leading to unpredictable behavior and potential conflicts.
