browser-compat-data Files

Breaking changes

This release introduces two breaking changes in the TypeScript definitions. The shape of the published data.json has not changed.

Summary: The published TypeScript definitions (types.d.ts) now fully match the actual shape of the published data.json. Two existing types are now stricter.

1. source_file is now required on CompatStatement (#29041)

Previously, the CompatStatement.source_file property was optional in the TypeScript definitions, even though it is always present in published data.json releases (it is generated at build time).

Now, source_file is typed as required, matching the actual shape of the data.

Impact: You may need to remove checks for a missing source_file (e.g. if (compat.source_file)).

2. BrowserStatement.upstream is narrowed to UpstreamBrowserName (#29041)

Previously, the BrowserStatement.upstream property was typed as BrowserName, allowing any of the 17 known browser keys.

Now, upstream is typed as the new UpstreamBrowserName, a subset of BrowserName containing only the browsers that other browsers actually derive from: "chrome" | "chrome_android" | "firefox" | "safari" | "safari_ios".

Impact: You may need to widen the type when passing upstream into functions expecting a full BrowserName, or switch on the narrower set.

Statistics

• 2 contributors have changed 91 files with 1,681 additions and 784 deletions in 1 commit (v7.3.17...v8.0.0)
• 19,752 total features
• 1,250 total contributors
• 5,671 total stargazers