[WIP] V4

.github/workflows/ci.yml

@@ -46,7 +46,7 @@ jobs:
       - run: npm ci
       - run: npx run-s bundle test-unit-bun
 
-  promises-and-observables:
+  promises:
     strategy:
       matrix:
         node:
@@ -62,7 +62,7 @@ jobs:
           node-version: ${{ matrix.node }}
           cache: npm
       - run: npm ci
-      - run: npx run-s test-promises test-observables
+      - run: npm run test-promises
 
   tests:
     strategy:

.gitignore

@@ -7,37 +7,37 @@ node_modules/
 *.swp
 .DS_Store
 
-/packages/core-js/features/
-/packages/core-js/es/index.js
-/packages/core-js/full/index.js
-/packages/core-js/stable/index.js
+/packages/core-js/actual/
+/packages/core-js/es/
+/packages/core-js/full/
+/packages/core-js/proposals/
+/packages/core-js/stable/
+/packages/core-js/stage/
+/packages/core-js/index.js
 /packages/core-js/LICENSE
 /packages/core-js-builder/LICENSE
 /packages/core-js-bundle/LICENSE
 /packages/core-js-bundle/index.js
 /packages/core-js-bundle/minified.js
 /packages/core-js-bundle/minified.js.map
-/packages/core-js-bundle/postinstall.js
 /packages/core-js-compat/LICENSE
+/packages/core-js-compat/built-in-definitions.json
 /packages/core-js-compat/data.json
 /packages/core-js-compat/entries.json
 /packages/core-js-compat/external.json
 /packages/core-js-compat/modules.json
 /packages/core-js-compat/modules-by-versions.json
 /packages/core-js-pure/actual/
 /packages/core-js-pure/es/
-/packages/core-js-pure/features/
 /packages/core-js-pure/full/
 /packages/core-js-pure/internals/
 /packages/core-js-pure/modules/
 /packages/core-js-pure/proposals/
 /packages/core-js-pure/stable/
 /packages/core-js-pure/stage/
-/packages/core-js-pure/web/
 /packages/core-js-pure/LICENSE
 /packages/core-js-pure/index.js
 /packages/core-js-pure/configurator.js
-/packages/core-js-pure/postinstall.js
 /tests/**/bundles/
 /tests/compat/*.jar
 /tests/compat/compat-data.js

CONTRIBUTING.md

@@ -12,21 +12,21 @@ There is always some ["help wanted" issues](https://github.com/zloirock/core-js/
 - The polyfill should properly work in ES3 and all possible engines. If in some engines it cannot be implemented (for example, it striuctly requires more modern ES or unavailable platform features), it should not break any other `core-js` features or application in any way.
 - Avoid possible observing / breakage polyfills via patching built-ins at runtime: cache all global built-ins in the polyfills code and don't call prototype methods from instances.
 - Shared helpers should be added to the [`packages/core-js/internals`](./packages/core-js/internals) directory. Reuse already existing helpers.
-- Avoid direct import from `/modules/` path in `/internals|modules/` since it will break optimizations via Babel / `swc`. Specify such dependencies in `/es|stable|actual/full/` entries and use something like [`internals/get-built-in`](./packages/core-js/modules/get-built-in.js) helpers.
+- Avoid direct import from `/modules/` path in `/internals|modules/` since it will break optimizations via Babel / `swc`. Specify such dependencies with comments like `// dependency: es.string.iterator` directly in your module, they will be automatically added to entries, and use something like [`internals/get-built-in`](./packages/core-js/modules/get-built-in.js) helpers.
 - For export the polyfill, in all common cases use [`internals/export`](./packages/core-js/modules/export.js) 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`](./packages/core-js/modules/is-pure.js) constant 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.
+- 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`](./packages/core-js/modules/is-pure.js) constant 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), 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 it to entries definitions, see [`scripts/build-entries/entries-definitions.mjs`](./scripts/build-entries/entries-definitions.mjs).
 - Add unit tests to [`tests/unit-global`](./tests/unit-global) and [`tests/unit-pure`](./tests/unit-pure).
 - Add tests of entry points to [`tests/entries/unit.mjs`](./tests/entries/unit.mjs).
 - Make sure that you are following [our coding style](#style-and-standards) and [all tests](#testing) are passed.
 - Document it in [README.md](./README.md) and [CHANGELOG.md](./CHANGELOG.md).
 
 [A simple example of adding a new polyfill.](https://github.com/zloirock/core-js/pull/1294/files)
 
-## How to update `core-js-compat` data
+## How to update `@core-js/compat` data
 
-For updating `core-js-compat` data:
+For updating `@core-js/compat` data:
 
 - If you want to add a new data for a browser, run in this browser `tests/compat/index.html` (tests and results for the actual release are available at [`http://zloirock.github.io/core-js/compat/`](http://zloirock.github.io/core-js/compat/)) and you will see what `core-js` modules are required for this browser.
 
@@ -42,27 +42,26 @@ For updating `core-js-compat` data:
 
 engine            | how to run tests | base data inherits from    | mandatory check  | mapping for a new version
 ---               | ---              | ---                        | ---              | ---
-`android`         | browser runner   | `chrome`, `chrome-android` |                  |
+`android`         | browser runner   | `chrome`, `chrome_mobile`  |                  |
 `bun`             | bun runner       | `safari` (only ES)         | required         |
 `chrome`          | browser runner   |                            | required         |
-`chrome-android`  | browser runner   | `chrome`                   |                  |
+`chrome_mobile`   | browser runner   | `chrome`                   |                  |
 `deno`            | deno runner      | `chrome` (only ES)         | non-ES features  | required
 `edge`            | browser runner   | `ie`, `chrome`             | required (<= 18) |
 `electron`        | browser runner   | `chrome`                   |                  | required
 `firefox`         | browser runner   |                            | required         |
-`firefox-android` | browser runner   | `firefox`                  |                  |
+`firefox_mobile`  | browser runner   | `firefox`                  |                  |
 `hermes`          | hermes runner    |                            | required         |
 `ie`              | browser runner   |                            | required         |
 `ios`             | browser runner   | `safari`                   |                  | if inconsistent (!= `safari`)
 `node`            | node runner      | `chrome` (only ES)         | non-ES features  | required
 `opera`           | browser runner   | `chrome`                   |                  | if inconsistent (!= `chrome` - 14)
-`opera-android`   | browser runner   | `opera`, `chrome-android`  |                  | required
-`phantom`         | browser runner   | `safari`                   |                  |
-`quest`           | browser runner   | `chrome-android`           |                  | required
-`react-native`    | hermes runner    | `hermes`                   | required         |
+`opera_mobile`    | browser runner   | `opera`, `chrome_mobile`   |                  | required
+`quest`           | browser runner   | `chrome_mobile`            |                  | required
+`react_native`    | hermes runner    | `hermes`                   | required         |
 `rhino`           | rhino runner     |                            | required         |
 `safari`          | browser runner   |                            | required         |
-`samsung`         | browser runner   | `chrome-android`           |                  | required
+`samsung`         | browser runner   | `chrome_mobile`            |                  | required
 
 If you have no access to all required browsers / versions of browsers, use [Sauce Labs](https://saucelabs.com/), [BrowserStack](https://www.browserstack.com/) or [Cloud Browser](https://ieonchrome.com/).
 
@@ -73,7 +72,7 @@ The coding style should follow our [`eslint.config.js`](./tests/eslint/eslint.co
 - Unit tests should use the modern syntax with our [minimalistic Babel config](./babel.config.js). Unit tests for the pure version should not use any modern standard library features.
 - Tools, scripts and tests, performed in NodeJS, should use only the syntax and the standard library available in NodeJS 8.
 
-File names should be in the kebab-case. Name of polyfill modules should follow the naming convention `namespace.subnamespace-where-required.feature-name`, for example, `esnext.set.intersection`. The top-level namespace should be `es` for stable ECMAScript features, `esnext` for ECMAScript proposals and `web` for other web standards.
+File names should be in the kebab-case. Name of polyfill modules should follow the naming convention `namespace.subnamespace-where-required.feature-name`, for example, `es.set.intersection`. The top-level namespace should be `es` for stable ECMAScript features, `esnext` for ECMAScript proposals and `web` for other web standards.
 
 ## Testing
 
@@ -110,19 +109,15 @@ You can run parts of the test case separately:
   ```sh
   npx run-s prepare test-promises
   ```
-- [ECMAScript `Observable` test case](https://github.com/tc39/proposal-observable):
-  ```sh
-  npx run-s prepare test-observables
-  ```
 - CommonJS entry points tests:
   ```sh
   npx run-s prepare test-entries
   ```
-- `core-js-compat` tools tests:
+- `@core-js/compat` tools tests:
   ```sh
   npx run-s prepare test-compat-tools
   ```
-- `core-js-builder` tests:
+- `@core-js/builder` tests:
   ```sh
   npx run-s prepare test-builder
   ```