Version Details and Security Vulnerabilities

📦

@swc/core

1.3.4

Comparision Betweeen 1.3.4 and 1.3.3

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

629.17 KB

623.72 KB

Version 1.3.4 Details

@swc/core is a high-performance JavaScript and TypeScript compiler, designed as a faster alternative to Babel. Version 1.3.4 builds upon the solid foundation of its predecessor, 1.3.3, with nuanced yet impactful changes that benefit developers seeking optimal build times and efficient code transformation.

The core functionality remains consistent, offering super-fast compilation, but the key updates lie within the dependency tree. While both versions share a similar list of dependencies and optional dependencies related to platform-specific binaries (like @swc/core-darwin-x64 and others for various OS and architectures), the underlying versions of these platform-specific packages are bumped from 1.3.3 to 1.3.4 to stay aligned with the core package.This ensures compatibility and potentially includes bug fixes or performance improvements within those specific builds.

A notable change in the devDependencies is the update of swc-plugin-coverage-instrument from version 0.0.12 to 0.0.13. This suggests improvements or bug fixes related to code coverage instrumentation, a crucial aspect for testing and ensuring code quality.

Developers using @swc/core should upgrade to 1.3.4 to leverage these improvements, especially if they rely on code coverage tooling. The update also includes the latest versions of platform-specific binaries, ensuring compatibility and potential performance gains across different operating systems. Although the vast majority of dependencies stayed on the same version, updating to the newest version 1.3.4 enables continued, seamless workflows and improved development experiences for those already integrated into the swc ecosystem. The minor version bump shows that the library is still stable and the migration should be easy, as it should not contain any big breaking changes.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.