Babel plugin transform async to generator provides a crucial transformation, converting modern async functions into ES2015 generator functions, enabling compatibility with older JavaScript environments. Comparing versions 6.1.17 and 6.1.13, the core functionality remains consistent: both empower developers to utilize the async/await syntax, streamlining asynchronous code management and improving readability. Essentially, this plugin acts as a bridge, allowing developers to leverage the benefits of asynchronous programming without alienating users on older browsers or environments that lack native async/await support.
The difference between the versions lies primarily in the updated dependencies. Version 6.1.17 relies on newer versions of babel-helper-remap-async-to-generator and babel-plugin-syntax-async-functions (both at ^6.1.17) compared to version 6.1.13 (both at ^6.1.13). These updates likely incorporate bug fixes, performance improvements, or enhanced compatibility with other Babel plugins and configurations. The babel-runtime remains at ^5.0.0 in both versions. Similarly, the devDependencies, specifically babel-helper-plugin-test-runner, is updated to ^6.1.17 in the newer version, suggesting improvements to the testing infrastructure. Developers choosing between the two should opt for version 6.1.17 to benefit from the latest bug fixes and dependency updates, ensuring a smoother and potentially more reliable transformation of asynchronous code. The library is MIT licensed and the source code can be found on Github.
All the vulnerabilities related to the version 6.1.17 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