Version Details and Security Vulnerabilities

📦

core-js

0.9.13

Comparision Betweeen 0.9.13 and 0.9.12

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.13 Details

Core-js version 0.9.13 is a minor patch release following version 0.9.12, both serving as standard library implementations. Examining the metadata, the core difference lies in the release date: version 0.9.13 was published on May 25, 2015, while version 0.9.12 was released on May 23, 2015. This two-day gap suggests that 0.9.13 likely contains bug fixes or minor improvements over its predecessor, however the data provided does not specify the nature of these changes. For developers using core-js, these versions provide essential polyfills for modern JavaScript features, ensuring compatibility across various environments, particularly older browsers.

Both versions share identical development dependencies, encompassing tools for building, testing, and linting the library. These include Grunt for task automation, Karma for test execution, ESLint for code quality, and Webpack for module bundling. The testing suite leverages promises-aplus-tests to maintain Promises/A+ compliance and utilizes various Karma launchers for cross-browser testing in Chrome, Firefox, PhantomJS, Opera, and IE. The consistent dependency structure implies a stable development workflow across both releases. Developers should consider reviewing the core-js changelog or commit history around May 2015 for detailed specifics regarding the updates incorporated in version 0.9.13. While seemingly minor, patch releases often address critical bugs or performance improvements, making the newer version the preferred choice for most users.

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.