source-map breaking changes

npm

10 curated breaking changes across major versions of source-map. Use this as a migration checklist before bumping dependencies.

View package health \u2192Known bugs \u2192
10
changes
Breaking changes by transition
  • 0.7.3 \u2192 0.7.4breaking

    [#350](https://github.com/mozilla/source-map/pull/350) -

  • 0.7.3 \u2192 0.7.4breaking

    [#363](https://github.com/mozilla/source-map/pull/363) -

  • 0.7.3 \u2192 0.7.4breaking

    [#362](https://github.com/mozilla/source-map/pull/362) -

  • 0.7.3 \u2192 0.7.4breaking

    [#371](https://github.com/mozilla/source-map/pull/371) -

  • 0.5.6 \u2192 0.7.0breaking

    `SourceMapConsumer` now uses WebAssembly, and is **much** faster! Read about

  • 0.5.6 \u2192 0.7.0breaking

    **Breaking change:** `new SourceMapConsumer` now returns a `Promise` object

  • 0.5.6 \u2192 0.7.0breaking

    **Breaking change:** when you're done using a `SourceMapConsumer` instance,

  • 0.5.6 \u2192 0.7.0breaking

    **Breaking change:** `SourceMapConsumer` used to be able to handle lines,

  • 0.5.6 \u2192 0.7.0breaking

    **Breaking change:** The `source-map` library now uses modern ECMAScript-isms:

  • 0.5.6 \u2192 0.7.0breaking

    **Breaking change:** Drop support for Node < 8. If you want to support older

API access

Get this data programmatically \u2014 free, no authentication.

curl https://depscope.dev/api/breaking/npm/source-map
source-map breaking changes — npm migration guide | DepScope