Version Details and Security Vulnerabilities

📦

core-js

3.3.0

Comparision Betweeen 3.3.0 and 3.2.1

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

1675

1604

Unpacked Size

607.8 KB

558.34 KB

Version 3.3.0 Details

Core-js version 3.3.0 represents an incremental update to the popular JavaScript standard library, building upon the foundation established in version 3.2.1. While both versions share the same core mission of providing polyfills and shims for modern ECMAScript features, enabling developers to write code that works across different JavaScript environments, version 3.3.0 introduces several refinements and additions that are relevant for developers concerned with staying on the cutting edge.

One noticeable difference is the increase in size, both in terms of fileCount and unpackedSize. The newer version includes more files (1675 compared to 1604) and a larger unpacked size (622384 versus 571737), suggesting additions of new features, improved polyfills or expanded test coverage. A 2 months development has been made between the 2 releases.

Developers considering an upgrade from 3.2.1 to 3.3.0 should focus new features of ECMAScript proposed in the updated version and improved or refined polyfills, potentially leading to better performance or compatibility across various browsers and Node.js versions. Examining the changelog or release notes associated with version 3.3.0 on the core-js GitHub repository is crucial to understand the specific changes and determine whether they address particular needs or resolve existing issues in their projects. Also, the date is relevant, since the update was released after 2 months of development, so some dependencies might be updated too.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.