Version Details and Security Vulnerabilities

📦

@swc/core

1.3.10

Comparision Betweeen 1.3.10 and 1.3.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

649.98 KB

644.71 KB

Version 1.3.10 Details

@swc/core versions 1.3.10 and 1.3.9 are both rapid JavaScript and TypeScript compilers designed as a high-performance alternative to Babel. Examining the metadata of the two releases reveals subtle differences, primarily consisting of version updates within their respective dependencies and optional dependencies.

Both versions list identical sets of devDependencies, including popular testing frameworks (Jest, Mocha), and development utilities (TypeScript, Prettier, ESLint), hinting their commitment to a solid development experience. While the listed devDependencies do not change between the two versions, developers looking to upgrade should still check if sub-dependencies of those tools may experience breaking changes.

The core difference between the two lies in the dependency versions of specific platform builds. Version 1.3.10 uses "@swc/core-{platform}":"1.3.10" for all platforms, while version 1.3.9 correspondingly uses "@swc/core-{platform}":"1.3.9". This indicates that the core compilation logic has been updated with platform-specific optimisations or bug fixes in the newer release. Developers should check the Changlog file available on swc-project GitHub repo to understand if any specific bug fix or feature will affect them.

The unpacked size of version 1.3.10 is also slightly larger (665579 bytes) compared to 1.3.9 (660181 bytes), further supporting the idea that improvements affecting runtime were included. The release dates of October 21, 2022, and October 17, 2022, respectively, provide a clear timeline for when these updates were available. Consequently, developers should opt for the latest version (1.3.10) to benefit from the newest features, performance enhancements, and bug fixes, especially for projects relying on specific platform targets like Darwin, Linux, or Windows.

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.