Back to Explore

jridgewell/sourcemaps

GitHub
1 watchersOpen source

Last release: 8 months ago

A GitHub monorepo for various JavaScript sourcemap-related libraries, including gen-mapping, remapping, source-map, sourmap-codec, and trace-mapping. Useful for tooling that needs to generate, parse, encode, or trace source maps.

Project status

  • The upstream repo (jridgewell/sourcemaps), described as a monorepo for sourcemap libraries, shows evidence of ongoing activity (last upstream push on 2026-04-21), and recent update activity in the trace-mapping package (0.3.29 to 0.3.31 in 2025), suggesting it is actively maintained rather than abandoned.
  • The apparent update cadence for trace-mapping is roughly every 3 to 6 weeks in 2025 (0.3.29 on 2025-07-01, 0.3.30 on 2025-08-12, 0.3.31 on 2025-09-10), indicating a continuing development rhythm though not necessarily a fixed schedule.

AI summary generated Today

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • trace-mapping/0.3.31

    8 months ago

    trace-mapping v0.3.31 makes an internal change focused on improving performance of `generatedPositionFor`. The only explicit release documentation in-repo is a changelog entry mentioning that performance improvement, but the code diff shows a deeper refactor in how generated positions are indexed by source.

  • trace-mapping/0.3.30

    9 months ago

    trace-mapping/0.3.30 has no publisher-provided release notes, and the diff shows internal build and packaging changes rather than API additions. The main changes are around how the library is exported (conditional exports and UMD interop), plus patch-level dependency bumps within the @jridgewell sourcemaps toolchain.

  • trace-mapping/0.3.29

    11 months ago

    trace-mapping version 0.3.29 was released on 2025-07-01. No release notes or change log details were provided, so the upgrade impact (features, fixes, breaking changes, security updates, or dependency changes) is not described in the available material.

  • trace-mapping/0.3.28

    11 months ago

    trace-mapping/0.3.28 (and related @jridgewell packages) bumps package versions and primarily changes the build pipeline used to generate UMD/CJS bundles. The code diff updates esbuild's UMD wrapper generation and adds a getOwnPropertyDescriptors polyfill intended for very old Node versions (Node 6).

  • trace-mapping/0.3.27

    11 months ago

    trace-mapping/0.3.27 is primarily a packaging and module compatibility release. The main change is removal of the `module-sync` export condition, which is used for `require(esm)`-style consumption.

  • trace-mapping/0.3.26

    11 months ago

    trace-mapping version 0.3.26 was published, but the provided release notes are empty. The code diff shown for this release is dominated by large additions that introduce new packages (notably gen-mapping and remapping) and new monorepo tooling, rather than small trace-mapping-only edits.

    Features
  • trace-mapping/0.3.25

    3/2/2024

    trace-mapping version 0.3.25 refactors how source map inputs are typed and parsed, especially around nested sectioned maps. Release notes were not provided, so the documented behavior cannot be validated against what changed; the diff shows type export and typing compatibility changes, plus internal parsing adjustments.

    Breaking
  • trace-mapping/0.3.24

    3/1/2024

    trace-mapping/0.3.24 introduces support for source map v3 ignore lists via a new ignoreList field (and legacy x_google_ignoreList). It propagates ignoreList through AnyMap decoding and adds a new exported helper, isIgnored, to query whether a given source should be ignored.

    Features
  • trace-mapping/0.3.23

    2/24/2024

    No release notes were provided for trace-mapping/0.3.23. The code diff shows a significant internal refactor in the source map tracing implementation (TraceMap and related exported helpers), along with CI and test tooling changes (Node versions, AVA to Mocha).

  • trace-mapping/0.3.22

    1/19/2024

    The trace-mapping v0.3.22 release was published on 2024-01-19, but no release notes were provided by the publisher. Because the release notes are missing, this analysis cannot identify specific new features, bug fixes, breaking changes, security updates, or dependency changes from the provided information.