Version Details and Security Vulnerabilities

📦

core-js

0.9.7

Comparision Betweeen 0.9.7 and 0.9.6

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 0.9.7 Details

Core-js version 0.9.7 is a minor update to the popular standard library, building upon the foundation laid by version 0.9.6. Both versions offer robust implementations of ECMAScript features, providing developers with polyfills and shims necessary to support older browsers and environments. The key difference lies in the release date: 0.9.7 was published on May 7th, 2015, while 0.9.6 was released on May 1st, 2015, suggesting that version 0.9.7 likely includes bug fixes, performance improvements, or small feature enhancements not present in the earlier release.

For developers leveraging core-js, this means updating to version 0.9.7 is advisable to benefit from the latest refinements. Both versions share the same suite of development dependencies, including tools like Grunt, Karma, ESLint, and Webpack, ensuring a consistent build and testing process. Core-js continues to be licensed under the permissive MIT license, granting flexibility for integration into various projects. The package is available via npm and its source code is hosted on GitHub, encouraging community contributions. While the specific changes between 0.9.6 and 0.9.7 aren't explicitly detailed in the provided metadata, the update suggests an effort to maintain a stable and up-to-date ECMAScript environment for developers targeting multiple platforms. The presence of Promises A+ tests also underlines the library's commitment to adhering to well-defined specifications and providing reliable implementations.

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.