Babel-preset-stage-2 is a crucial tool for JavaScript developers using Babel to transpile their code, enabling them to leverage features from ECMAScript stage 2 proposals. This preset provides access to functionalities that are on track for official standardization, offering a glimpse into the future of JavaScript development. Comparing versions 6.0.15 and 6.1.2 reveals subtle but important changes in dependency management. The key difference lies in the required version of babel-preset-stage-3. Version 6.0.15 depends on babel-preset-stage-3 at version ^6.0.15, while version 6.1.2 upgrades this dependency to ^6.1.2. This suggests that the newer version incorporates improvements or bug fixes present in the corresponding update to the subsequent stage preset.
Both versions, however, share the same dependencies for babel-plugin-transform-object-rest-spread and babel-plugin-syntax-trailing-function-commas, both pinned to version 6.0.14. This indicates stability in these specific transformations.
Developers should upgrade to version 6.1.2 primarily to ensure compatibility and benefit from potential enhancements within the babel-preset-stage-3 dependency. Staying current with these presets ensures access to the most refined implementations of upcoming JavaScript features, and reduces the risk of relying on outdated or buggy transpilation rules. Although the changes appear minor, adhering to the latest minor version can promote a smoother development workflow and more predictable behavior when using stage 2 features in your JavaScript projects. It's important to review the changelog for babel-preset-stage-3 6.1.2 to understand the precise nature of the update.
All the vulnerabilities related to the version 6.1.2 of the package
Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code
Using Babel to compile code that was specifically crafted by an attacker can lead to arbitrary code execution during compilation, when using plugins that rely on the path.evaluate()or path.evaluateTruthy() internal Babel methods.
Known affected plugins are:
@babel/plugin-transform-runtime@babel/preset-env when using its useBuiltIns option@babel/helper-define-polyfill-provider, such as babel-plugin-polyfill-corejs3, babel-plugin-polyfill-corejs2, babel-plugin-polyfill-es-shims, babel-plugin-polyfill-regeneratorNo other plugins under the @babel/ namespace are impacted, but third-party plugins might be.
Users that only compile trusted code are not impacted.
The vulnerability has been fixed in @babel/traverse@7.23.2.
Babel 6 does not receive security fixes anymore (see Babel's security policy), hence there is no patch planned for babel-traverse@6.
@babel/traverse to v7.23.2 or higher. You can do this by deleting it from your package manager's lockfile and re-installing the dependencies. @babel/core >=7.23.2 will automatically pull in a non-vulnerable version.@babel/traverse and are using one of the affected packages mentioned above, upgrade them to their latest version to avoid triggering the vulnerable code path in affected @babel/traverse versions:
@babel/plugin-transform-runtime v7.23.2@babel/preset-env v7.23.2@babel/helper-define-polyfill-provider v0.4.3babel-plugin-polyfill-corejs2 v0.4.6babel-plugin-polyfill-corejs3 v0.8.5babel-plugin-polyfill-es-shims v0.10.0babel-plugin-polyfill-regenerator v0.5.3