Back to Explore

web-platform-dx/baseline-browser-mapping

GitHub
1 watchersOpen source

Last release: 3 months ago

baseline-browser-mapping provides browser version data for the W3C WebDX Baseline feature sets. Use getCompatibleVersions() to get the minimum compatible browser versions for Baseline Widely available and Baseline year features, or use getAllVersions() to retrieve support details for multiple Baseline feature sets across browser versions. It is updated frequently to stay current with underlying browser-compatibility data, and can warn if the installed data is older than about 2 months.

Project status

  • The source appears actively maintained, with recent tagged updates (v2.10.0 on 2026-02-19, v2.9.3 on 2025-12-05, v2.9.2 on 2025-12-04) and a very recent upstream push on 2026-05-30.
  • The apparent update cadence is moderately frequent, with two updates in early December 2025 (v2.9.2 and v2.9.3) followed by a next update in mid-February 2026 (v2.10.0).

AI summary generated Today

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

Recent updates

  • v2.10.0

    3 months ago

    v2.10.0 focuses on enabling older Node runtimes (including Node 6) by refactoring code paths that rely on newer JS built-ins and adjusting the build targets and CLI implementation. It also adds CI test coverage across a Node version matrix and updates the publish workflows to use NPM OIDC-style publishing permissions. Separately, the bundled browser data is refreshed with updated release dates/statuses and added downstream browser versions.

    Features
  • v2.9.3

    5 months ago

    v2.9.3 removes the library's automatic call to Node's process.loadEnvFile() during module initialization. It updates documentation and tests to reflect that .env loading must be handled by the consumer before calling baseline-browser-mapping.

    Breaking
  • v2.9.2

    6 months ago

    v2.9.2 is labeled as a browser support bug fix. The code changes focus on making the library safe to import and run in browser-like environments where Node's global `process` (and `process.exit`) may be missing.

  • v2.9.0

    6 months ago

    v2.9.0 changes the “data staleness” warning behavior so warnings are emitted only when consumers call `getCompatibleVersions()` or `getAllVersions()`, rather than during module load. It also adds suppression controls via a new `suppressWarnings` option and environment variables, and updates warning text and README guidance for reproducible builds.

    Features
  • v2.8.4

    8 months ago

    v2.8.4 is described as a compatibility-focused release for older Node.js versions. The documented changes are primarily around build target transpilation (ES2017) and adjusting how CommonJS entrypoints are exposed via package.json main.

    Breaking
  • v2.8.0

    8 months ago

    v2.8.0 primarily adds baseline mapping support for Facebook and Instagram Android apps. The code diff, however, shows a broader dataset regeneration that updates multiple existing browser entries (Safari, Firefox) and Widely Available/newly statuses, plus bumps in key dev dependencies.

    Features
  • v2.7.4

    9 months ago

    v2.7.4 is described as a module size reduction by removing web-features IDs from the compressed baseline mapping dataset. The code diff shows that this change also altered the internal compressed data schema and the downstream data expansion logic, alongside large updates to the bundled baseline data itself.

  • v2.7.0

    9 months ago

    v2.7.0 adds opt-in KaiOS support to the library by introducing a new includeKaiOS option for getCompatibleVersions and getAllVersions. It also updates downstream browser datasets, including removing an erroneous Yandex browser version (99.9) that had been introduced earlier.

    Features
  • v2.6.6

    9 months ago

    v2.6.6 is a data patch release that updates the library's embedded browser-version and feature compatibility mappings. The release notes provide only a compare link and no description of functional changes, but the diff shows multiple dataset and publishing workflow changes that can alter computed Baseline and Widely Available results.

  • v2.6.3

    9 months ago

    v2.6.3 is labeled as a data patch, but the release notes only provide a compare link and do not enumerate any changes. The actual diff shows modifications to the core data set (adding a new feature, removing an existing one, and changing version mappings) plus dependency bumps for MDN browser compatibility data and web-features.

    BreakingFeatures