Version Details and Security Vulnerabilities

📦

@swc/core

1.7.18

Comparision Betweeen 1.7.18 and 1.7.14

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.41 KB

Version 1.7.18 Details

@swc/core, a super-fast alternative to Babel, has released version 1.7.18, building upon the previous stable version 1.7.14. Both versions share the same core dependencies, including "@swc/types" and "@swc/counter", as well as development dependencies like Jest, cross-env, TypeScript, and @napi-rs/cli, which are essential for testing and development workflows. They also maintain the consistent peer dependency on "@swc/helpers".

A primary distinction lies within the "optionalDependencies" section. While both versions offer pre-built binaries for various platforms, including Darwin (macOS), Linux, and Windows, supporting different architectures like x64, ARM64, and ia32, the version number associated with each platform-specific binary reflects the core package version. Thus, version 1.7.18 uses binaries tagged with "1.7.18" and version 1.7.14 accordingly.

For developers, this means that upgrading from 1.7.14 to 1.7.18 ensures they're utilizing the latest optimizations and bug fixes tailored to their specific operating system and architecture. The optional dependencies facilitate seamless installation and optimized performance, leveraging native binaries when available. The core functionality advertised as a super-fast babel alternative remains consistent, driven by a strong focus on performance. The new version was released on 2024-08-24 and the previous stable version was released on 2024-08-19, so there are 5 days in between the releases.

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.