3.19.0

Author: zloirock

CHANGELOG.md

@@ -1,5 +1,8 @@
 ## Changelog
 ##### Unreleased
+- Nothing
+
+##### 3.19.0 - 2021.10.25
 - Most built-ins are encapsulated in `core-js` for preventing possible cases of breaking / observing the internal state by patching / deleting of them
   - Avoid `.call` / `.apply` prototype methods that could be patched
   - Avoid `instanceof` operator - implicit `.prototype` / `@@hasInstance` access that could be patched

README.md

@@ -140,14 +140,14 @@ Promise.resolve(32).then(x => console.log(x)); // => 32
 ### Installation:[⬆](#index)
 ```
 // global version
-npm install --save core-js@3.18.3
+npm install --save core-js@3.19.0
 // version without global namespace pollution
-npm install --save core-js-pure@3.18.3
+npm install --save core-js-pure@3.19.0
 // bundled global version
-npm install --save core-js-bundle@3.18.3
+npm install --save core-js-bundle@3.19.0
 ```
 
-Already bundled version of `core-js` [on CDN](https://unpkg.com/core-js-bundle@3.18.3) ([minified version](https://unpkg.com/core-js-bundle@3.18.3/minified.js)).
+Already bundled version of `core-js` [on CDN](https://unpkg.com/core-js-bundle@3.19.0) ([minified version](https://unpkg.com/core-js-bundle@3.19.0/minified.js)).
 
 ### `postinstall` message[⬆](#index)
 The `core-js` project needs your help, so the package shows a message about it after installation. If it causes problems for you, you can disable it:
@@ -237,9 +237,9 @@ import 'regenerator-runtime/runtime';
 
 #### `@babel/preset-env`[⬆](#index)
 
-[`@babel/preset-env`](https://github.com/babel/babel/tree/master/packages/babel-preset-env) has `useBuiltIns` option, which optimizes working with global version of `core-js`. With `useBuiltIns` option, you should also set `corejs` option to used version of `core-js`, like `corejs: '3.18'`.
+[`@babel/preset-env`](https://github.com/babel/babel/tree/master/packages/babel-preset-env) has `useBuiltIns` option, which optimizes working with global version of `core-js`. With `useBuiltIns` option, you should also set `corejs` option to used version of `core-js`, like `corejs: '3.19'`.
 
-> **Warning!** Recommended to specify used minor `core-js` version, like `corejs: '3.18'`, instead of `corejs: 3`, since with `corejs: 3` will not be injected modules which were added in minor `core-js` releases.
+> **Warning!** Recommended to specify used minor `core-js` version, like `corejs: '3.19'`, instead of `corejs: 3`, since with `corejs: 3` will not be injected modules which were added in minor `core-js` releases.
 
 - `useBuiltIns: 'entry'` replaces imports of `core-js` to import only required for a target environment modules. So, for example,
 ```js
@@ -294,7 +294,7 @@ import 'core-js/modules/es.array.of';
 var array = Array.of(1, 2, 3);
 ```
 
-By default, `@babel/preset-env` with `useBuiltIns: 'usage'` option only polyfills stable features, but you can enable polyfilling of proposals by `proposals` option, as `corejs: { version: '3.18', proposals: true }`.
+By default, `@babel/preset-env` with `useBuiltIns: 'usage'` option only polyfills stable features, but you can enable polyfilling of proposals by `proposals` option, as `corejs: { version: '3.19', proposals: true }`.
 
 #### `@babel/runtime`[⬆](#index)
 

deno/corejs/README.md

@@ -24,7 +24,7 @@
 
 *Example*:
 ```js
-import 'https://deno.land/x/corejs@v3.18.3/index.js'; // <- at the top of your entry point
+import 'https://deno.land/x/corejs@v3.19.0/index.js'; // <- at the top of your entry point
 
 Object.hasOwn({ foo: 42 }, 'foo'); // => true