Babel plugin transform async to generator, versions 6.3.0 and 6.3.13, provides the functionality to convert async functions into ES2015 generators, offering compatibility for environments not natively supporting async/await syntax. Both versions share the same core function, enabling developers to leverage modern asynchronous programming techniques while targeting older JavaScript runtimes. The key benefit is simplifying asynchronous code management, reducing callback hell and improving code readability by transforming async functions into a more manageable generator-based structure.
A notable difference lies in the versioning of their dependencies. Version 6.3.13 updates babel-helper-remap-async-to-generator and babel-plugin-syntax-async-functions to version 6.3.13, while 6.3.0 relies on babel-helper-remap-async-to-generator at version 6.3.0 and babel-plugin-syntax-async-functions at version 6.1.18. Similarly, the babel-helper-plugin-test-runner dev dependency is updated from 6.1.18 to 6.3.13 in the newer version. This indicates potential bug fixes, performance enhancements, or added features within these helper and syntax packages incorporated into version 6.3.13. Developers upgrading should consider potential minor breaking changes, though the core functionality remains consistent. The bump in dependencies suggests a refinement and stabilization focus in the newer release, making it a potentially more reliable choice for new projects. Both versions depend on babel-runtime at ^5.0.0, ensuring a consistent runtime environment.
All the vulnerabilities related to the version 6.3.13 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