Version Details and Security Vulnerabilities

📦

@swc/core

1.10.11

Comparision Betweeen 1.10.11 and 1.10.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

116.07 KB

116.05 KB

Version 1.10.11 Details

@swc/core is a high-performance JavaScript and TypeScript compiler, sought after as a faster alternative to Babel. Examining versions 1.10.11 and 1.10.9, reveals subtle but important differences. Both share the same core architecture, dependencies on @swc/types and @swc/counter, and development dependencies that include testing (Jest), environment configuration (cross-env), type checking (Typescript) and native addon building (@napi-rs/cli). Both versions also share the use of @swc/helpers as peer dependencies and the same optional dependencies for different architectures. The descriptions, license, repository details, author, and funding information is consistent between versions.

The primary distinction lies in the version numbers of the core package and its optional dependencies tailored to specific platforms (darwin, linux, win32) and architectures (x64, arm64, ia32). Version 1.10.11 ships with all core & optionals dependencies being 1.10.11, while 1.10.9 has everything on 1.10.9. Crucially, unpackedSize value has increased from 118840 to 118851, meaning some files are larger. The releaseDate of 1.10.11 is six days after 1.10.9. While the changelogs are not provided, developers should consider these factors to determine whether the newer version provides sufficient bug fixes, performance improvements, or new features to justify an upgrade. Review the official changelog for a comprehensive view of the updates and their impact on projects.

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.