Version Details and Security Vulnerabilities

📦

@swc/core

1.1.27

Comparision Betweeen 1.1.27 and 1.1.26

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

328.72 KB

361.18 KB

Version 1.1.27 Details

@swc/core, a blazing-fast alternative to Babel, released version 1.1.27 following closely on the heels of version 1.1.26. Both versions maintain the core functionality of accelerating JavaScript and TypeScript compilation, offering developers a significant performance boost over traditional tools. They share identical dependencies, including mkdirp, progress, node-fetch, and true-case-path, ensuring consistent behavior in crucial file system operations, build process feedback, network requests, and accurate path resolution. The development dependencies remain the same as well, meaning there are no changes to the testing, linting or type checking toolchain. Both versions include popular tools for compiling and transforming JavaScript like Babel and Typescript compiler, with corresponding presets and plugins.

The key difference lies in the updated dist metadata. Version 1.1.27 boasts a smaller unpacked size of 336613 compared to version 1.1.26's 369853. This reduction suggests potential optimizations in the compiled output, leading to a leaner final bundle size for end-users, an important aspect for web performance. This means the newer version *may* have better cold starts than the old version. Because the package size has been reduced, it may mean that some unused code has been removed, and that is a good thing for javascript libraries. The release date also differs, with version 1.1.27 being released on February 20, 2020, and version 1.1.26 the day before, meaning the newer version includes the latest fixes and improvments. Developers should consider upgrading to version 1.1.27 to benefit from these potential size and stability improvements, ensuring optimal performance and resource utilization in their 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.