Version Details and Security Vulnerabilities

📦

@swc/core

1.2.116

Comparision Betweeen 1.2.116 and 1.2.115

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

124

Unpacked Size

716.68 KB

716.66 KB

Version 1.2.116 Details

@swc/core is a high-performance JavaScript and TypeScript compiler designed as a faster alternative to Babel. Version 1.2.116 introduces incremental improvements over the previous stable version, 1.2.115, primarily focusing on core dependencies related to different operating systems and architectures. Both versions share the same core purpose: accelerating the build process for web applications. Developers will appreciate the consistent set of features and capabilities for compiling modern JavaScript and TypeScript code.

The key difference lies in the platform-specific dependencies. Both versions feature @swc/core-* packages for various environments, including Darwin (macOS), FreeBSD, Linux, and Windows across different architectures (x64, ARM64, ia32). The core dependencies, like @node-rs/helper, remain largely unchanged, ensuring compatibility and stability. The devDependencies offer a comprehensive toolkit for testing and development, encompassing popular libraries like Jest, React, and TypeScript, indicating a robust testing environment. The optionalDependencies mirror the dependencies, which suggests that these platform-specific packages will be downloaded based on the platform used and the core package will run without throwing an error if they are not present.

For developers considering incorporating SWC into their workflow, both versions offer a compelling solution for speeding up compilation times. While the functional differences between the two versions might be minimal, staying up-to-date with the latest release ensures that you're leveraging the most recent performance tweaks and bug fixes within the SWC ecosystem. The consistency in devDependencies also allows developers to use the same tools to test both versions of the packages making upgrades less painful.

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.