unstale

npm / baseline-browser-mapping

baseline-browser-mapping

What changed in baseline-browser-mapping 2, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-14.

2 breaking3 new APIs and options3 behavior and defaults2 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.3.1 on npm

baseline-browser-mapping 210 changes

Breaking changes 2

  • Unsupported option combinations now throw an Error instead of calling process.exit(), allowing more graceful handling.

    2.11.0release notessecurity advisory

  • The main script no longer calls process.loadEnfFile().

    2.9.3release notes

New APIs and options 3

  • Adds a method to get the series of minimum browser changes, grouped by date or by browser.

    2.11.0release notes

  • Adds an environment variable to suppress data staleness warnings.

    2.9.0release notes

  • Adds a boolean option to suppress data staleness warnings.

    2.9.0release notes

Behavior and default changes 3

  • Node 6 is supported; package.json specifies support for Node versions >=6.0.0, and the CLI avoids APIs unavailable before Node 18.

    2.10.0release notes

  • Warnings are shown only when getCompatibleVersions() or getAllVersions() is called, rather than whenever the module is loaded.

    2.9.0release notes

  • Warnings are limited to cases where feature cutoff data is within the last two months and module data is more than two months old.

    2.9.0release notes

Fixes and other changes 2

  • Fixes a browser support bug.

    2.9.2release notes

  • The package now respects this existing environment variable to suppress data staleness warnings.

    2.9.0release notes