Version Details and Security Vulnerabilities

📦

es6-promise

4.2.0

Comparision Betweeen 4.2.0 and 4.1.1

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 4.2.0 Details

Es6-promise version 4.2.0 introduces several updates compared to the previous stable version 4.1.1. Both versions serve as lightweight libraries designed to streamline asynchronous code management, a core need for modern JavaScript development. The primary distinctions lie in the upgraded development dependencies, reflecting advancements in the tooling ecosystem.

Notably, mocha which is a Javascript test framework jumps from version 3.1.0 to 4.0.1, ember-cli which is a command line utility for ember from 2.12.2 to 2.17.1, along with a significant shift in the Babel transpilation setup. Version 4.2.0 utilizes a suite of granular Babel plugins (babel-plugin-transform-es2015-*), enabling more targeted ES6 feature support compared to the earlier version that relied on broccoli-babel-transpiler. This allows for finer control over the transpilation process and potential performance improvements.

Furthermore, version 4.2.0 removes the release-it and ember-publisher dependencies, indicating a potential change in the release process or tooling. The inclusion of babel6-plugin-strip-class-callcheck suggests an optimization effort to reduce unnecessary runtime checks. The update of other tools like git-repo-version, broccoli-stew, broccoli-rollup, ember-cli-dependency-checker ensures compatibility with the latest features and bug fixes provided by those tools.

For developers, this update means potentially enhanced performance through optimized Babel transpilation and access to the latest features and fixes in supporting development tools. While the core functionality of the promise library remains consistent, the updated development dependencies in version 4.2.0 offer a more modern and potentially more efficient development workflow.

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.