Version Details and Security Vulnerabilities

📦

@babel/plugin-transform-runtime

7.24.7

Comparision Betweeen 7.24.7 and 7.24.6

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

102.12 KB

102.14 KB

Version 7.24.7 Details

@babel/plugin-transform-runtime version 7.24.7 is a minor release following 7.24.6, primarily focused on internal updates and dependency synchronization within the Babel ecosystem. It aims to improve the stability and compatibility of the plugin with the latest Babel tooling.

A key task of this plugin is automatically polyfilling your code, handling references to helpers and built-ins. This process avoids polluting the global scope. Both versions maintain the same core dependencies for polyfilling core-js features and regenerator runtime. The dependencies section, including babel-plugin-polyfill-corejs2 and babel-plugin-polyfill-corejs3, remains consistent between the two versions, ensuring continued support for various ECMAScript versions.

The significant change lies within the devDependencies. Version 7.24.7 updates the development dependencies such as @babel/core, @babel/helpers, @babel/runtime, @babel/preset-env, @babel/runtime-corejs3, and @babel/helper-plugin-test-runner all to version 7.24.7. This synchronization ensures that the plugin is tested and developed against the latest versions of these core Babel packages. The babel-plugin-polyfill-corejs3 version stays the same.

For developers, this upgrade implies enhanced reliability and potentially improved build performance due to the synchronized Babel dependencies. If you're already using Babel 7.24.6 or earlier, upgrading to 7.24.7 is recommended to benefit from these internal improvements and maintain compatibility with the wider Babel ecosystem. While there are no listed new features, keeping your Babel plugins up-to-date ensures optimal performance and reduces the risk of encountering compatibility issues. The unpacked size decreased negligibly from 104588 to 104568 so probably there were changes in the comments or code formatting.

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.