Version Details and Security Vulnerabilities

📦

core-js

3.4.0

Comparision Betweeen 3.4.0 and 3.3.6

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

1678

1677

Unpacked Size

614.06 KB

612.73 KB

Version 3.4.0 Details

Core-js version 3.4.0 builds upon the foundation of version 3.3.6, offering incremental improvements and refinements to this widely used JavaScript standard library. Both versions, licensed under MIT, provide developers with essential polyfills and shims that ensure consistent JavaScript functionality across different browsers and environments. From a developer's perspective, the upgrade from 3.3.6 to 3.4.0 introduces a few key changes that while seemingly small could improve performances avoiding possible bugs.

While the number of files included in the package remains relatively consistent (1678 in 3.4.0 vs. 1677 in 3.3.6), there's a slight increase in the unpacked size (628800 bytes vs. 627437 bytes). This suggests the addition of new features, refined implementations, or updated data tables within the library. Though file count might have increased with just one file, the unpacked size shows an increase of more than 1KB, which might be related to increased verbosity with comments.

Developers considering updating should be aware of these subtle changes, which likely encompass bug fixes, performance enhancements, and possibly the inclusion of new or updated proposals from the ECMAScript standard. Checking the library's changelog or release notes is a recommended action that can give more hints about the changes between the two versions. While both versions share the same core functionality and licensing terms, the newer version likely benefits from the iterative improvements and refinements that often accompany software development cycles. Version 3.4.0 was released on 2019-11-06, just a few days apart from the previous version making the fixes included important to keep libraries updated.

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.