Version Details and Security Vulnerabilities

📦

@swc/core

1.2.96

Comparision Betweeen 1.2.96 and 1.2.95

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

156.18 KB

156.25 KB

Version 1.2.96 Details

Version 1.2.96 of @swc/core, a high-performance JavaScript and TypeScript compiler, was released on October 14, 2021, following closely after version 1.2.95 released on October 9, 2021. Both versions share the same fundamental purpose: to offer a speedy alternative to Babel for developers seeking faster build times. The core functionality and the vast majority of dependencies, including crucial tools like jest, typescript, and various Babel plugins and presets, remain consistent between the two versions, ensuring a stable and familiar development experience.

The key difference lies in the platform-specific binary dependencies. While both depend on @node-rs/helper, each @swc/core package wraps platform-specific binaries. Version 1.2.95 had the @swc/core-freebsd-x64 compiled binary while version 1.2.96 removed that optional dependency. This indicates a change of supported compiling targets.

The development team, led by 강동윤, continues to refine the core compilation engine, improving performance and expanding compatibility. Developers using @swc/core can anticipate faster build times and seamless integration with existing JavaScript toolchains. Both versions are licensed under Apache-2.0 AND MIT, with funding supported through Open Collective, ensuring the project's sustainability and continued development. Upgrading from 1.2.95 to 1.2.96 will primarily impact developers targeting FreeBSD, potentially requiring adjustments to their build processes if they were relying on the removed binary. However, for most users, the transition should be smooth, offering the same benefits of rapid compilation and a modern JavaScript/TypeScript workflow.

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.