@babel/preset-env, a popular Babel preset that enables developers to use the latest JavaScript features while ensuring compatibility with different environments, saw a minor update from version 7.13.0 to 7.13.5. While the core functionalities remain consistent, there are subtle but noteworthy changes.
A key difference lies in the updated dependencies. Notably, @babel/compat-data receives an update from version 7.13.0 to 7.13.5, reflecting enhancements and refinements in supported JavaScript features and their corresponding compatibility data. This ensures more accurate and up-to-date transpilation behavior. Furthermore, babel-plugin-polyfill-corejs2 and babel-plugin-polyfill-corejs3 were updated from version 0.1.2 to 0.1.4 and 0.1.3 respectively together with babel-plugin-polyfill-regenerator from 0.1.1 to 0.1.2. @babel/plugin-proposal-async-generator-functions also evolved from version 7.13.0 to 7.13.5. These upgrades signify improvements in polyfilling capabilities for older environments, crucial for developers targeting a wide range of browsers.
For developers, these changes mean improved accuracy and reliability when using @babel/preset-env. The updated @babel/compat-data translates to better handling of modern JavaScript syntax, while refined polyfills ensure wider compatibility without unexpected behavior. When upgrading from 7.13.0, developers should see seamless improvements in code transpilation and runtime support. However, reviewing your configuration and dependencies is always a good practice after updating any Babel-related package. These subtle adjustments often optimize the transpilation process, ensuring that code runs smoothly across targeted environments.
All the vulnerabilities related to the version 7.13.5 of the package
semver vulnerable to Regular Expression Denial of Service
Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.