core.js

WebJar for core.js

License	License MIT
Categories	Categories JavaScript Languages Github Development Tools Version Controls
GroupId	GroupId org.webjars.bower
ArtifactId	ArtifactId github-com-zloirock-core-js
Last Version	Last Version 2.5.3
Release Date	Release Date Jan 25, 2018
Type	Type jar
Description	Description core.js WebJar for core.js
Project URL	Project URL http://webjars.org
Source Code Management	Source Code Management https://github.com/zloirock/core-js

Download github-com-zloirock-core-js

Filename	Size
github-com-zloirock-core-js-2.5.3.pom
github-com-zloirock-core-js-2.5.3.jar	1 MB
github-com-zloirock-core-js-2.5.3-sources.jar	22 bytes
github-com-zloirock-core-js-2.5.3-javadoc.jar	22 bytes
Browse

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/org.webjars.bower/github-com-zloirock-core-js/ -->
<dependency>
    <groupId>org.webjars.bower</groupId>
    <artifactId>github-com-zloirock-core-js</artifactId>
    <version>2.5.3</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/org.webjars.bower/github-com-zloirock-core-js/
implementation 'org.webjars.bower:github-com-zloirock-core-js:2.5.3'

Gradle Kotlin

// https://jarcasting.com/artifacts/org.webjars.bower/github-com-zloirock-core-js/
implementation ("org.webjars.bower:github-com-zloirock-core-js:2.5.3")

Apache Buildr

'org.webjars.bower:github-com-zloirock-core-js:jar:2.5.3'

Apache Ivy

<dependency org="org.webjars.bower" name="github-com-zloirock-core-js" rev="2.5.3">
  <artifact name="github-com-zloirock-core-js" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='org.webjars.bower', module='github-com-zloirock-core-js', version='2.5.3')
)

Scala SBT

libraryDependencies += "org.webjars.bower" % "github-com-zloirock-core-js" % "2.5.3"

Leiningen

[org.webjars.bower/github-com-zloirock-core-js "2.5.3"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

There are no modules declared in this project.

core-js

Modular standard library for JavaScript. Includes polyfills for ECMAScript up to 2021: promises, symbols, collections, iterators, typed arrays, many other features, ECMAScript proposals, some cross-platform WHATWG / W3C features and proposals like URL. You can load only required features or use it without global namespace pollution.

If you looking documentation for obsolete core-js@2, please, check this branch.

As advertising: the author is looking for a good job -)

core-js@3, babel and a look into the future

Raising funds

core-js isn't backed by a company, so the future of this project depends on you. Become a sponsor or a backer on Open Collective or on Patreon if you are interested in core-js.

For enterprise

Available as part of the Tidelift Subscription.

The maintainers of core-js and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.

Example of usage:

import 'core-js'; // <- at the top of your entry point

Array.from(new Set([1, 2, 3, 2, 1]));          // => [1, 2, 3]
[1, [2, 3], [4, [5]]].flat(2);                 // => [1, 2, 3, 4, 5]
Promise.resolve(32).then(x => console.log(x)); // => 32

You can load only required features:

import 'core-js/features/array/from'; // <- at the top of your entry point
import 'core-js/features/array/flat'; // <- at the top of your entry point
import 'core-js/features/set';        // <- at the top of your entry point
import 'core-js/features/promise';    // <- at the top of your entry point

Array.from(new Set([1, 2, 3, 2, 1]));          // => [1, 2, 3]
[1, [2, 3], [4, [5]]].flat(2);                 // => [1, 2, 3, 4, 5]
Promise.resolve(32).then(x => console.log(x)); // => 32

Or use it without global namespace pollution:

import from from 'core-js-pure/features/array/from';
import flat from 'core-js-pure/features/array/flat';
import Set from 'core-js-pure/features/set';
import Promise from 'core-js-pure/features/promise';

from(new Set([1, 2, 3, 2, 1]));                // => [1, 2, 3]
flat([1, [2, 3], [4, [5]]], 2);                // => [1, 2, 3, 4, 5]
Promise.resolve(32).then(x => console.log(x)); // => 32

Index

Usage ⬆

Installation: ⬆

// global version
npm install --save [email protected]
// version without global namespace pollution
npm install --save [email protected]
// bundled global version
npm install --save [email protected]

Already bundled version of core-js on CDN (minified version).

`postinstall` message ⬆

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:

ADBLOCK=true npm install
// or
DISABLE_OPENCOLLECTIVE=true npm install
// or
npm install --loglevel silent

CommonJS API ⬆

You can import only-required-for-you polyfills, like in examples at the top of README.md. Available CommonJS entry points for all polyfilled methods / constructors and namespaces. Just some examples:

// polyfill all `core-js` features:
import "core-js";
// polyfill only stable `core-js` features - ES and web standards:
import "core-js/stable";
// polyfill only stable ES features:
import "core-js/es";

// if you want to polyfill `Set`:
// all `Set`-related features, with ES proposals:
import "core-js/features/set";
// stable required for `Set` ES features and features from web standards
// (DOM collections iterator in this case):
import "core-js/stable/set";
// only stable ES features required for `Set`:
import "core-js/es/set";
// the same without global namespace pollution:
import Set from "core-js-pure/features/set";
import Set from "core-js-pure/stable/set";
import Set from "core-js-pure/es/set";

// if you want to polyfill just required methods:
import "core-js/features/set/intersection";
import "core-js/stable/queue-microtask";
import "core-js/es/array/from";

// polyfill reflect metadata proposal:
import "core-js/proposals/reflect-metadata";
// polyfill all stage 2+ proposals:
import "core-js/stage/2";

Caveats when using CommonJS API: ⬆

modules path is an internal API, does not inject all required dependencies and can be changed in minor or patch releases. Use it only for a custom build and/or if you know what are you doing.
If you use core-js with the extension of native objects, recommended load all core-js modules at the top of the entry point of your application, otherwise, you can have conflicts.
- For example, Google Maps use their own Symbol.iterator, conflicting with Array.from, URLSearchParams and/or something else from core-js, see related issues.
- Such conflicts also resolvable by discrovering and manual adding each conflicting entry from core-js.
core-js is extremely modular and uses a lot of very tiny modules, because of that for usage in browsers bundle up core-js instead of usage loader for each file, otherwise, you will have hundreds of requests.

CommonJS and prototype methods without global namespace pollution ⬆

In the pure version, we can't pollute prototypes of native constructors. Because of that, prototype methods transformed into static methods like in examples above. But with transpilers, we can use one more trick - bind operator and virtual methods. Special for that, available /virtual/ entry points. Example:

import fill from 'core-js-pure/features/array/virtual/fill';
import findIndex from 'core-js-pure/features/array/virtual/find-index';

Array(10)::fill(0).map((a, b) => b * b)::findIndex(it => it && !(it % 8)); // => 4

// or

import { fill, findIndex } from 'core-js-pure/features/array/virtual';

Array(10)::fill(0).map((a, b) => b * b)::findIndex(it => it && !(it % 8)); // => 4

Babel ⬆

core-js is integrated with babel and is the base for polyfilling-related babel features:

`@babel/polyfill` ⬆

@babel/polyfill IS just the import of stable core-js features and regenerator-runtime for generators and async functions, so if you load @babel/polyfill - you load the global version of core-js without ES proposals.

Now it's deprecated in favour of separate inclusion of required parts of core-js and regenerator-runtime and, for preventing breaking changes, left on core-js@2.

As a full equal of @babel/polyfill, you can use this:

import 'core-js/stable';
import 'regenerator-runtime/runtime';

`@babel/preset-env` ⬆

@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.8'.

Warning! Recommended to specify used minor core-js version, like corejs: '3.8', 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,

import 'core-js/stable';

with chrome 71 target will be replaced just to:

import "core-js/modules/es.array.unscopables.flat";
import "core-js/modules/es.array.unscopables.flat-map";
import "core-js/modules/es.object.from-entries";
import "core-js/modules/web.immediate";

It works for all entry points of global version of core-js and their combinations, for example for

import 'core-js/es';
import 'core-js/proposals/set-methods';
import 'core-js/features/set/map';

with chrome 71 target you will have as a result:

import "core-js/modules/es.array.unscopables.flat";
import "core-js/modules/es.array.unscopables.flat-map";
import "core-js/modules/es.object.from-entries";
import "core-js/modules/esnext.set.difference";
import "core-js/modules/esnext.set.intersection";
import "core-js/modules/esnext.set.is-disjoint-from";
import "core-js/modules/esnext.set.is-subset-of";
import "core-js/modules/esnext.set.is-superset-of";
import "core-js/modules/esnext.set.map";
import "core-js/modules/esnext.set.symmetric-difference";
import "core-js/modules/esnext.set.union";

useBuiltIns: 'usage' adds to the top of each file import of polyfills for features used in this file and not supported by target environments, so for:

// first file:
var set = new Set([1, 2, 3]);

// second file:
var array = Array.of(1, 2, 3);

if target contains an old environment like IE 11 we will have something like:

// first file:
import 'core-js/modules/es.array.iterator';
import 'core-js/modules/es.object.to-string';
import 'core-js/modules/es.set';
var set = new Set([1, 2, 3]);

// second file:
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.8', proposals: true }.

`@babel/runtime` ⬆

@babel/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:

import from from 'core-js-pure/stable/array/from';
import flat from 'core-js-pure/stable/array/flat';
import Set from 'core-js-pure/stable/set';
import Promise from 'core-js-pure/stable/promise';

from(new Set([1, 2, 3, 2, 1]));
flat([1, [2, 3], [4, [5]]], 2);
Promise.resolve(32).then(x => console.log(x));

you can write just:

Array.from(new Set([1, 2, 3, 2, 1]));
[1, [2, 3], [4, [5]]].flat(2);
Promise.resolve(32).then(x => console.log(x));

By default, @babel/runtime only polyfills stable features, but like in @babel/preset-env, you can enable polyfilling of proposals by proposals option, as corejs: { version: 3, proposals: true }.

Warning! If you use @babel/preset-env and @babel/runtime together, use corejs option only in one place since it's duplicate functionality and will cause conflicts.

Configurable level of aggressiveness ⬆

By default, core-js sets polyfills only when they are required. That means that core-js checks if a feature is available and works correctly or not and if it has no problems, core-js use native implementation.

But sometimes core-js feature detection could be too strict for your case. For example, Promise constructor requires the support of unhandled rejection tracking and @@species.

Sometimes we could have inverse problem - knowingly broken environment with problems not covered by core-js feature detection.

For those cases, we could redefine this behaviour for certain polyfills:

const configurator = require('core-js/configurator');

configurator({
  useNative: ['Promise'],                                 // polyfills will be used only if natives completely unavailable
  usePolyfill: ['Array.from', 'String.prototype.padEnd'], // polyfills will be used anyway
  useFeatureDetection: ['Map', 'Set'],                    // default behaviour
});

require('core-js');

It does not work with some features. Also, if you change the default behaviour, even core-js internals may not work correctly.

Custom build ⬆

For some cases could be useful to exclude some core-js features or generate a polyfill for target engines. You could use core-js-builder package for that.

Compatibility data ⬆

core-js-compat package contains data about the necessity of core-js modules and API for getting a list of required core-js modules by browserslist query.

Supported engines ⬆

Tested in:

Chrome 26+
Firefox 4+
Safari 5+
Opera 12+
Internet Explorer 8+ (sure, IE8 with ES3 limitations; IE7- also should work, but no longer tested)
Edge
Android Browser 2.3+
iOS Safari 5.1+
PhantomJS 1.9+
NodeJS 0.8+

...and it doesn't mean core-js will not work in other engines, they just have not been tested.

core.js

License

Categories

GroupId

ArtifactId

Last Version

Release Date

Type

Description

Project URL

Source Code Management

Download github-com-zloirock-core-js

How to add to project

Dependencies

Project Modules

core-js

As advertising: the author is looking for a good job -)

Raising funds

For enterprise

Index

Usage ⬆

Installation: ⬆

postinstall message ⬆

CommonJS API ⬆

Caveats when using CommonJS API: ⬆

CommonJS and prototype methods without global namespace pollution ⬆

Babel ⬆

@babel/polyfill ⬆

@babel/preset-env ⬆

@babel/runtime ⬆

Configurable level of aggressiveness ⬆

Custom build ⬆

Compatibility data ⬆

Supported engines ⬆

Features: ⬆

ECMAScript ⬆

ECMAScript: Object ⬆

ECMAScript: Function ⬆

ECMAScript: Array ⬆

ECMAScript: String and RegExp ⬆

ECMAScript: Number ⬆

ECMAScript: Math ⬆

ECMAScript: Date ⬆

ECMAScript: Promise ⬆

Unhandled rejection tracking ⬆

ECMAScript: Symbol ⬆

Caveats when using Symbol polyfill: ⬆

ECMAScript: Collections ⬆

Map ⬆

Set ⬆

WeakMap ⬆

WeakSet ⬆

Caveats when using collections polyfill: ⬆

ECMAScript: Typed Arrays ⬆

Caveats when using typed arrays polyfills: ⬆

ECMAScript: Reflect ⬆

ECMAScript: JSON ⬆

ECMAScript: globalThis ⬆

ECMAScript proposals ⬆

Stage 4 proposals ⬆

Stage 3 proposals ⬆

Stage 2 proposals ⬆

Caveats: ⬆

Stage 1 proposals ⬆

New collections methods: ⬆

Stage 0 proposals ⬆

Pre-stage 0 proposals ⬆

Web standards ⬆

setTimeout and setInterval ⬆

setImmediate ⬆

queueMicrotask ⬆

URL and URLSearchParams ⬆

Caveats when using URL and URLSearchParams: ⬆

Iterable DOM collections ⬆

Iteration helpers ⬆

Missing polyfills ⬆

Versions

`postinstall` message ⬆

`@babel/polyfill` ⬆

`@babel/preset-env` ⬆

`@babel/runtime` ⬆

Caveats when using `Symbol` polyfill: ⬆

`setTimeout` and `setInterval` ⬆

`setImmediate` ⬆

`queueMicrotask` ⬆

`URL` and `URLSearchParams` ⬆

Caveats when using `URL` and `URLSearchParams`: ⬆