Version Details and Security Vulnerabilities

📦

@babel/plugin-transform-runtime

7.28.0

Comparision Betweeen 7.28.0 and 7.27.4

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

37.33 KB

Version 7.28.0 Details

@babel/plugin-transform-runtime versions 7.28.0 and 7.27.4 serve the same core function: externalizing references to Babel's helpers and built-ins, enabling automatic polyfilling without polluting the global scope. This is crucial for developers aiming to create cleaner, more compatible JavaScript code, especially targeting older browsers. Both versions rely on @babel/helper-plugin-utils and @babel/helper-module-imports, indicating a consistent approach to plugin utilities and module import handling.

Key differences lie in the dependency versions, reflecting improvements and bug fixes in the underlying polyfilling and core Babel infrastructure. Version 7.28.0 upgrades babel-plugin-polyfill-corejs2 from 0.4.10 to 0.4.14, babel-plugin-polyfill-corejs3 from 0.11.0 to 0.13.0, and babel-plugin-polyfill-regenerator from 0.6.1 to 0.6.5. These updates signify enhanced support for newer JavaScript features through core-js and Regenerator, crucial for developers leveraging modern syntax. The @babel/core, @babel/helpers, @babel/runtime, @babel/preset-env, and @babel/runtime-corejs3 development dependencies are also bumped, indicating a move to newer Babel features.

For developers, upgrading to 7.28.0 means getting updated polyfills and potentially improved ES syntax transformations, benefiting from the newest features available in Javascript. The bump in babel-plugin-polyfill-corejs3 is specially important because it specifies how the package manager supports and integrates the core-js library within the newest ES versions.

Both versions maintain the same size and file count, suggesting no significant changes to the core logic but focus on refining the polyfilling and integration processes.

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.