@cspotcode/source-map-support adds source map support to Node.js so stack traces show original source file paths and line numbers instead of compiled JavaScript locations. It uses the V8 stack trace API and the source-map module, and can be enabled via a CLI require hook, a `register` import, or programmatic `install()`.
Project status
- The source does not appear actively maintained as of 2026-08-13, with the last upstream push on 2023-07-05 and no update history shown after 2022 (a multi year gap suggests it is quiet or in maintenance mode).
- Update cadence appears low and irregular: several updates happened in 2020 to 2022 (for example v0.5.18 to v0.8.1), but no evidence of frequent or ongoing updates in the last couple of years.
AI summary generated
Recent updates
v0.8.1
Release v0.8.1 updates the package version metadata and makes a small change to how error strings are constructed when preparing stack traces. No release notes were provided, so the behavioral impact of the code change is not documented.
v0.8.0
Release v0.8.0 has no publisher-provided release notes. The diff shows a substantial internal change in how source maps are processed (switching the underlying mapping library), plus related updates to cache key handling and URL/path normalization in stack trace formatting.
BreakingFeaturesv0.7.0
Release v0.7.0 was published on 2021-10-10, but no release notes were provided by the publisher. As a result, there is no documented information about new features, breaking changes, bug fixes, or security updates in this release.
v0.6.1
Release v0.6.1 updates the package version from 0.6.0 to 0.6.1. The code diff indicates changes limited to package metadata (repository and bugs URLs) and corresponding version fields in package.json and package-lock.json, with no application logic changes shown.
v0.6.0
v0.6.0 introduces a package rebrand and a number of runtime behavior changes around stack trace formatting and fatal error output. Release notes were not provided, so the analysis below is based entirely on the observed code and packaging diffs.
BreakingFeaturesv0.5.19
Release v0.5.19 has no release notes provided. The code diff indicates internal packaging changes and a specific update to how `exports.install` loads Node's `module` when `options.hookRequire` is enabled.
v0.5.18
Release v0.5.18 updates the source-map-support package (and its bundled browser build) with small internal changes. There are no release notes provided, so the only documented information is the version bump itself.
v0.5.17
Release v0.5.17 updates the package metadata and introduces a code change in source-map-support’s uncaughtException handling logic for Node.js worker threads. No release notes were provided, so the behavioral impact of the worker-thread logic is not documented.
v0.5.16
This release updates the source-map-support package from v0.5.15 to v0.5.16. The code diff shows only minimal changes, mainly around how the library handles the internal state.nextPosition value when overriding CallSite.getFunctionName.
v0.5.15
Release v0.5.15 was published on 2019-10-28, but the publisher did not provide any release notes. No specific changes, fixes, or migration guidance can be extracted from the provided information.