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:
- Do not show a version number, whether one is provided.
- 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.