Version Details and Security Vulnerabilities

📦

@swc/core

1.7.10

Comparision Betweeen 1.7.10 and 1.7.9

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

117.32 KB

117.31 KB

Version 1.7.10 Details

@swc/core, a super-fast alternative to Babel, has released version 1.7.10, a minor update following version 1.7.9. Both versions share identical core dependencies on @swc/types and @swc/counter, suggesting stability in fundamental functionality. Similarly, their development dependencies (jest, cross-env, typescript, @napi-rs/cli) remain unchanged, indicating a consistent development environment and testing approach. The peer dependency @swc/helpers also persists, ensuring compatibility with existing SWC ecosystems. Crucially, the core logic relating to transpilation and code transformation appears consistent between the two versions, based on the dependencies.

The main difference lies within the optionalDependencies. Version 1.7.10 offers updated pre-built binaries for various platforms, including Darwin (x64 and arm64), Linux (x64 GNU and musl, arm64 GNU and musl, and arm-gnueabihf), and Windows (x64 MSVC, ia32 MSVC, and arm64 MSVC), all bumped to version 1.7.10. These platform-specific binaries cater to diverse operating systems and architectures, potentially optimizing performance by leveraging native code. The previous version, 1.7.9, included the corresponding binaries at version 1.7.9. The unpacked size of the new version is also slightly larger, going from 120125 to 120136, which suggests internal changes.

For developers choosing between the two, version 1.7.10 is the recommended choice, especially when deploying on specific platforms. It includes the latest optimizations catered to each system and might include bug fixes related to the platform specific binaries that were not available on the previous release. This approach allows SWC to deliver tailored performance advantages across different environments. Both versions are licensed under Apache-2.0 and actively maintained via GitHub.

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.