web-features is the package that describes Web platform features and provides Baseline status reports.
Subscribe to the Upcoming changes announcements thread for news about upcoming releases, such as breaking changes or major features.
npm install web-features
import { browsers, features, groups, snapshots } from "web-features";
Or, without Node.js:
import data from "web-features/data.json" with { type: "json" };
const { browsers, features, groups, snapshots } = data;
To import the JSON schema with or without Node.js:
import schema from "web-features/data.schema.json" with { type: "json" };
If you're using web-features
to render Baseline iconography or browser logos with support markers, then you must follow the name and logo usage guidelines.
For Baseline iconography, follow this procedure for each feature:
-
If
status.baseline
is"high"
, then show an affirmative "widely available" icon. -
If
status.baseline
is"low"
, then show an affirmative "newly available" icon. -
If
status.baseline
isfalse
, then show a "limited availability" non-Baseline icon.Note: All features that have the
discouraged
property are, by definition, non-Baseline, andstatus.baseline
will befalse
. If a feature has thediscouraged
property, consider showing a message describing the feature's discouraged status instead of Baseline iconography. Showing Baseline iconography for discouraged features may confuse readers. -
If
status.baseline
isundefined
, then do not show any Baseline or non-Baseline badge.
For browser support iconography (that is, browser logos and checkmarks and Xs), follow this procedure for each browser:
- If
status.baseline
is"high"
or"low"
, then show a green checkmark (✅, "supported") beside each browser's logo icon. - If
status.baseline
isfalse
and the browser'sstatus.support
key (for example,status.support.edge
) isundefined
orfalse
, then show a gray X ("unsupported") beside the browser's logo icon. - If
status.baseline
is"high"
or"low"
and the browser'sstatus.support
key is a string, then show a green checkmark ("supported") beside the browser's logo icon.
If you wish to report browser version numbers, avoid showing version numbers alone. Developers and users often do not know whether a version number refers to a very recent or old release. If you must show a version number, consider contextualizing that number by showing a release date, a relative date (such as "Released … years ago"), an offset (such as "… releases ago"), or usage statistics relevant to your audience (such as "…% of your visitors in the last 90 days").