Babel Preset Env simplifies JavaScript transpilation by allowing developers to target specific browser environments rather than writing complex Babel configurations manually. Versions 1.0.0 and 1.0.1 of babel-preset-env offer similar core functionality, sharing a robust set of dependencies and devDependencies. Both leverage key Babel plugins to transform ES2015+ code, including support for arrow functions, classes, destructuring, and more, ensuring compatibility across older browsers. They also share the same development dependencies, like eslint for code linting and mocha for testing which indicates a consistent development and testing environment across versions.
The key difference lies in the release date, with version 1.0.1 being published approximately 19 hours after version 1.0.0. While the data doesn't explicitly state the changes, this small time gap suggests that version 1.0.1 likely includes minor bug fixes, performance improvements, or documentation updates rather than any major feature additions. For developers, this means upgrading from 1.0.0 to 1.0.1 is likely a safe and straightforward process, minimizing potential breaking changes, therefore upgrading is recommended in order to keep your project up to date with the latest fixes. While version 1.0.0 is a stable version, it would be wise to upgrade. Both versions aim to make modern JavaScript development more accessible by providing a tailored compilation process.
All the vulnerabilities related to the version 1.0.1 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