# update-db **Repository Path**: feesow/update-browserslist-db ## Basic Information - **Project Name**: update-db - **Description**: No description available - **Primary Language**: Unknown - **License**: MIT - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2025-12-14 - **Last Updated**: 2025-12-14 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Update Browserslist DB Browserslist logo by Anton Popov CLI tool to update `caniuse-lite` with browsers DB from [Browserslist](https://github.com/browserslist/browserslist/) config. Some queries like `last 2 versions` or `>1%` depend on actual data from `caniuse-lite`. ```sh npx update-browserslist-db@latest ``` Or if using `pnpm`: ```sh pnpm exec update-browserslist-db latest ``` Or if using `yarn`: ```sh yarn dlx update-browserslist-db@latest ``` Sponsored by Evil Martians ## Why you need to call it regularly `npx update-browserslist-db@latest` updates `caniuse-lite` version in your npm, yarn, or pnpm lock file. This update will bring data about new browsers to polyfill tools like Autoprefixer or Babel and reduce already unnecessary polyfills. You need to do it regularly for three reasons: 1. To use the latest browser’s versions and statistics in queries like `last 2 versions` or `>1%`. For example, if you created your project 2 years ago and did not update your dependencies, `last 1 version` will return 2-year-old browsers. 2. Actual browser data will lead to using less polyfills. It will reduce size of JS and CSS files and improve website performance. 3. `caniuse-lite` deduplication: to synchronize versions in different tools. ## Security Contact To report a security vulnerability, please use the [Tidelift security contact]. Tidelift will coordinate the fix and disclosure. [Tidelift security contact]: https://tidelift.com/security