Babel-preset-stage-2 is a valuable tool for JavaScript developers seeking to leverage features nearing standardization. These two versions, 6.2.4 and the prior 6.1.18, offer a glimpse into the evolution of JavaScript support within the Babel ecosystem. The core functionality, providing a preset of plugins aligned with ECMAScript stage 2 proposals, remains consistent, enabling developers to experiment with and adopt promising new syntax and features.
A key difference lies in the synchronized versioning of its dependencies. Both versions rely on babel-preset-stage-3, babel-plugin-transform-object-rest-spread, and babel-plugin-syntax-trailing-function-commas. However, version 6.2.4 bumps these dependencies to their respective 6.2.4 releases, while 6.1.18 holds them at 6.1.18. This suggests that the newer version includes updates and potential bug fixes within these core plugins, offering a more refined and stable experience. Developers should note that the update in dependencies could introduce subtle behavioral changes or compatibility improvements, impacting how their code is transpiled. The move to synchronized versioning also helps ensure that the various components of the stage-2 preset are consistent and tested together.
Choosing between versions depends on a developer's specific needs. For projects prioritizing stability and extensive prior testing, sticking with version 6.1.18 may be safer. However, developers eager for the latest enhancements and bug fixes in the underlying plugins should consider upgrading to 6.2.4, while carefully evaluating the impact of dependency updates on existing code. Both versions provide access to features like object rest/spread properties and trailing function commas, facilitating more concise and expressive JavaScript code.
All the vulnerabilities related to the version 6.2.4 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