The browsers UXF builds and tests for, as a shareable browserslist
config. It is the single source of the minimum versions: tools read it, @uxf/eslint-config checks web APIs
against it, and the wiki page for people and the wording for clients follow from it.
caniuse keeps no version history for Chrome and Firefox on Android, so and_chr >= 121 and and_ff >= 121 resolve
to the newest version only; the desktop entries carry the actual floor.
What these versions mean for devices, why they were chosen, and the wording for offers and contracts: uxf-wiki,
44-development/standards/podpora-prohlizecu.md.
In the package.json of every app that is built for the browser (web, backoffice …; browserslist looks for the
nearest one upwards, so in a workspace monorepo the root one serves all its apps):
{
"browserslist": ["extends @uxf/browserslist-config"]
}
Next.js then compiles JavaScript and CSS for these browsers instead of its built-in default, and Autoprefixer and other browserslist-aware tools follow. Next.js ignores a config it cannot load and falls back to its default (Safari 16.4, Chrome 111), so check that the package is installed.
@uxf/eslint-config lists this package as a peer, so yarn dependencies:fix installs it. A project without
@uxf/scripts (no dependencies:fix) or without @uxf/eslint-config adds it by hand:
yarn add -D @uxf/browserslist-config. The browserslist field is always added by hand.
Check what the query resolves to with npx browserslist.
Change them here first, then the wiki page; the Google Doc for clients is exported from the wiki. Raising a minimum is a change for every project, so it goes into the release notes.