.eslintignore

@@ -4,3 +4,4 @@ node_modules/
 /packages/core-js-compat/*.json
 /packages/core-js-pure/override/
 /tests/bundles/
+/tests/compat/compat-data.js

.gitignore

@@ -39,5 +39,7 @@ node_modules/
 /packages/core-js-pure/configurator.js
 /packages/core-js-pure/postinstall.js
 /tests/bundles/
+/tests/compat/*.jar
+/tests/compat/compat-data.js
 /tests/tests/index.js
 /tests/pure/index.js

CHANGELOG.md

@@ -2,6 +2,13 @@
 ##### Unreleased
 - Nothing
 
+##### 3.22.4 - 2022.05.03
+- Ensured proper `.length` of polyfilled functions even in compressed code (excepting some ancient engines)
+- Ensured proper `.name` of polyfilled accessors (excepting some ancient engines)
+- Ensured proper source / `ToString` conversion of polyfilled accessors
+- Actualized Rhino compat data
+- Refactoring
+
 ##### 3.22.3 - 2022.04.28
 - Added a fix for FF99+ `Array.prototype.includes` broken on sparse arrays
 

CONTRIBUTING.md

@@ -8,23 +8,42 @@ Contributions are always welcome. If you don't know how you can help, you can ch
 - Shared helpers should be added to the [`packages/core-js/internals`](./packages/core-js/internals) directory. Reuse already existing helpers.
 - For export the polyfill, in all common cases use `internals/export` helper. Use something else only if this helper is not applicable - for example, if you want to polyfill accessors.
 - If the code of the pure version implementation should significantly differ from the global version (*that's not a frequent situation, in most cases `internals/is-pure` is enough*), you can add it to [`packages/core-js-pure/override`](./packages/core-js-pure/override) directory. The rest parts of `core-js-pure` will be copied from `core-js` package.
-- Add the feature detection of the polyfill to [`tests/compat/tests.js`](./tests/compat/tests.js), add the compatibility data to [`packages/core-js-compat/src/data.mjs`](./packages/core-js-compat/src/data.mjs) and the name of the polyfill module to [`packages/core-js-compat/src/modules-by-versions.mjs`](./packages/core-js-compat/src/modules-by-versions.mjs) (this data is also used for getting the default list of polyfills at bundling and generation indexes).
+- Add the feature detection of the polyfill to [`tests/compat/tests.js`](./tests/compat/tests.js), add the compatibility data to [`packages/core-js-compat/src/data.mjs`](./packages/core-js-compat/src/data.mjs), how to do it [see below](#how-to-update-core-js-compat-data), and the name of the polyfill module to [`packages/core-js-compat/src/modules-by-versions.mjs`](./packages/core-js-compat/src/modules-by-versions.mjs) (this data is also used for getting the default list of polyfills at bundling and generation indexes).
 - Add it to entry points where it's required: directories [`packages/core-js/es`](./packages/core-js/es), [`packages/core-js/stable`](./packages/core-js/stable), [`packages/core-js/actual`](./packages/core-js/actual), [`packages/core-js/full`](./packages/core-js/full), [`packages/core-js/proposals`](./packages/core-js/proposals), [`packages/core-js/stage`](./packages/core-js/stage) and [`packages/core-js/web`](./packages/core-js/web).
 - Add unit tests to [`tests/tests`](./tests/tests) and [`tests/pure`](./tests/pure).
 - Add tests of entry points to [`tests/commonjs.js`](./tests/commonjs.js).
 - Make sure that you are following [our coding style](#style-and-standards) and [all tests](#testing) are passed.
-- Documentat it in [README.md](./README.md) and [CHANGELOG.md](./CHANGELOG.md).
+- Document it in [README.md](./README.md) and [CHANGELOG.md](./CHANGELOG.md).
 
 ## How to update `core-js-compat` data
 
 For updating `core-js-compat` data:
 
-- If you want to add new data for a browser, run in this browser `tests/compat/index.html` and you will see what `core-js` modules are required for this browser.
-- If you want to add new data for NodeJS, run `npm run compat` with the installed required NodeJS version and you will see the results in the console. Use `npm run compat-json` if you want to get the result as JSON.
+- If you want to add new data for a browser, run in this browser [`tests/compat/index.html`](http://es6.zloirock.ru/compat/) and you will see what `core-js` modules are required for this browser.
+- If you want to add new data for NodeJS, run `npm run compat-node` with the installed required NodeJS version and you will see the results in the console. Use `npm run compat-node-json` if you want to get the result as JSON.
 - If you want to add new data for Deno, run `npm run compat-deno` with the installed required Deno version and you will see the results in the console. Use `npm run compat-deno-json` if you want to get the result as JSON.
+- If you want to add new data for Rhino, set the required Rhino version in `compat-rhino-prepare` NPM script in [`package.json`](./package.json), run `npm run compat-rhino` and you will see the results in the console.
 - After getting this data, add it to [`packages/core-js-compat/src/data.mjs`](./packages/core-js-compat/src/data.mjs).
 - If you want to add new mapping (for example, to add a new iOS Safari version based on Safari or NodeJS based on Chrome), add it to [`packages/core-js-compat/src/mapping.mjs`](./packages/core-js-compat/src/mapping.mjs).
 
+engine         | mandatory check | how to run tests | base data inherits from      | mapping for a new version
+---            | ---             | ---              | ---                          | ---
+`android`      |                 | browser runner   | `chrome`                     |
+`chrome`       | features        | browser runner   |                              |
+`deno`         | non-ES features | deno runner      | `chrome` (only ES)           | required
+`edge`         | features        | browser runner   | `ie` (<=18), `chrome` (>=74) |
+`electron`     |                 | browser runner   | `chrome`                     | required
+`firefox`      | features        | browser runner   |                              |
+`ie`           | features        | browser runner   |                              |
+`ios`          |                 | browser runner   | `safari`                     | required
+`node`         | non-ES features | node runner      | `chrome` (only ES)           | required
+`opera`        |                 | browser runner   | `chrome` (>12)               | in case of inconsistency
+`opera_mobile` |                 | browser runner   | `opera`, `chrome`            | required
+`phantom`      |                 | browser runner   | `safari`                     |
+`rhino`        | features        | rhino runner     |                              |
+`safari`       | features        | browser runner   |                              |
+`samsung`      |                 | browser runner   | `chrome`                     | required
+
 ## Style and standards
 
 The coding style should follow our [`.eslintrc`](./.eslintrc.js). You can test it by calling [`npm run lint`](#testing). Different places have different syntax and standard library limitations:

README.md

@@ -176,11 +176,11 @@ queueMicrotask(() => console.log('called as microtask'));
 ### Installation:[⬆](#index)
 ```
 // global version
-npm install --save core-js@3.22.3
+npm install --save core-js@3.22.4
 // version without global namespace pollution
-npm install --save core-js-pure@3.22.3
+npm install --save core-js-pure@3.22.4
 // bundled global version
-npm install --save core-js-bundle@3.22.3
+npm install --save core-js-bundle@3.22.4
 ```
 
 Or you can use `core-js` [from CDN](https://www.jsdelivr.com/package/npm/core-js-bundle).
@@ -336,6 +336,8 @@ 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.22', proposals: true }`.
 
+> **Warning!** In the case of `useBuiltIns: 'usage'`, you should not add `core-js` imports by yourself, they will be added automatically.
+
 #### `@babel/runtime`[⬆](#index)
 
 [`@babel/runtime`](https://babeljs.io/docs/plugins/transform-runtime/) with `corejs: 3` option simplifies work with `core-js-pure`. It automatically replaces usage of modern features from JS standard library to imports from the version of `core-js` without global namespace pollution, so instead of:
@@ -418,6 +420,7 @@ For some cases could be useful to exclude some `core-js` features or generate a
 - PhantomJS 1.9+
 - NodeJS 0.8+
 - Deno 1.0+
+- Rhino 1.7.14+
 
 ...and it doesn't mean `core-js` will not work in other engines, they just have not been tested.
 

deno/corejs/README.md

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