Version Details and Security Vulnerabilities

📦

@swc/core

1.10.2

Comparision Betweeen 1.10.2 and 1.10.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

116.05 KB

Version 1.10.2 Details

@swc/core is a high-performance JavaScript and TypeScript compiler written in Rust, positioning itself as a super-fast alternative to Babel. Versions 1.10.1 and 1.10.2 share nearly identical characteristics, both built upon the same core dependencies: @swc/types for handling data structures and @swc/counter for efficient counting operations. They also rely on the same suite of developer tools for testing (Jest), cross-environment support (cross-env), type checking (TypeScript), and native addon building (@napi-rs/cli). Notably, both versions maintain the same peer dependency on @swc/helpers, indicating a continued reliance on shared utility functions. Crucially, the optionalDependencies section is a key area for developers deploying to specific platforms; both versions provide pre-built binaries for various architectures, including Darwin (x64 and ARM64), Linux (x64 GNU/Musl, ARM64 GNU/Musl, ARM gnueabihf), and Windows (x64/IA32/ARM64 MSVC).

The primary difference lies in the versioning of these optional platform-specific binaries. Version 1.10.2 includes binaries specifically built for that version. If facing platform-specific issues or performance problems, ensuring you're using the correct binary is vital. From a developer standpoint, this upgrade suggests an incremental improvement or bug fix within the core compilation process or potentially adjustments in platform-specific optimizations. Developers should consult the changelog (typically available on the project's GitHub repository) for a detailed breakdown of changes incorporated in version 1.10.2. When upgrading, testers should check CI/CD or run automated tests to confirm compatibility. This helps ensure a smooth transition, especially for projects critical to platform-specific modules. Package size is the same and the release date is the main difference.

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.