browserslist 4.14.0 → 4.14.1

package/CHANGELOG.md

@@ -1,6 +1,9 @@
 # Change Log
 This project adheres to [Semantic Versioning](http://semver.org/).
 
+## 4.14.1
+* Added `--update-db` explanation (by Justin Zelinsky).
+
 ## 4.14
 * Add `BROWSERSLIST_DANGEROUS_EXTEND` support (by Timo Mayer).
 

package/README.md

@@ -70,6 +70,7 @@ Browserslist will take queries from tool option,
 
 * [Tools](#tools)
 * [Best Practices](#best-practices)
+* [Browsers Data Updating](#browsers-data-updating)
 * [Queries](#queries)
   * [Query Composition](#query-composition)
   * [Full List](#full-list)
@@ -143,6 +144,46 @@ Browserslist will take queries from tool option,
   and desktop Safari combined.
 
 
+## Browsers Data Updating
+
+`npx browserslist@latest --update-db` updates `caniuse-lite` version
+in your npm, yarn or pnpm lock file.
+
+You need to do it regularly for two 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. `caiuse-lite` deduplication: to synchronize version in different tools.
+
+> What is deduplication?
+
+Due to how npm architecture is setup, you may have a situation
+where you have multiple versions of a single dependency required.
+
+Imagine you begin a project, and you add `autoprefixer` as a dependency.
+npm looks for the latest `caniuse-lite` version (1.0.30000700) and adds it to
+`package-lock.json` under `autoprefixer` dependencies.
+
+A year later, you decide to add Babel. At this moment, we have a
+new version of `canuse-lite` (1.0.30000900). npm took the latest version
+and added it to your lock file under `@babel/preset-env` dependencies.
+
+Now your lock file looks like this:
+
+```ocaml
+autoprefixer 7.1.4
+  browserslist 3.1.1
+    caniuse-lite 1.0.30000700
+@babel/preset-env 7.10.0
+  browserslist 4.13.0
+    caniuse-lite 1.0.30000900
+```
+
+As you can see, we now have two versions of `caniuse-lite` installed.
+
+
 ## Queries
 
 Browserslist will use browsers and Node.js versions query
@@ -354,10 +395,11 @@ naming or prefixing the module with `@scope/browserslist-config`, such as
 `@scope/browserslist-config` or `@scope/browserslist-config-mycompany`.
 
 If you don’t accept Browserslist queries from users, you can disable the
-validation by using the `dangerousExtend` option:
+validation by using the or `BROWSERSLIST_DANGEROUS_EXTEND` environment variable
+or `dangerousExtend` option.
 
-```js
-browserslist(queries, { path, dangerousExtend: true })
+```sh
+BROWSERSLIST_DANGEROUS_EXTEND=1 npx webpack
 ```
 
 Because this uses `npm`'s resolution, you can also reference specific files

package/node.js

@@ -372,7 +372,10 @@ module.exports = {
     if (latest !== 0 && latest < halfYearAgo) {
       console.warn(
         'Browserslist: caniuse-lite is outdated. Please run:\n' +
-        'npx browserslist@latest --update-db'
+        'npx browserslist@latest --update-db\n' +
+        '\n' +
+        'Why you should do it regularly:\n' +
+        'https://github.com/browserslist/browserslist#browsers-data-updating'
       )
     }
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "browserslist",
-  "version": "4.14.0",
+  "version": "4.14.1",
   "description": "Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset",
   "keywords": [
     "caniuse",
@@ -15,8 +15,8 @@
   "license": "MIT",
   "repository": "browserslist/browserslist",
   "dependencies": {
-    "caniuse-lite": "^1.0.30001111",
-    "electron-to-chromium": "^1.3.523",
+    "caniuse-lite": "^1.0.30001124",
+    "electron-to-chromium": "^1.3.562",
     "escalade": "^3.0.2",
     "node-releases": "^1.1.60"
   },