Version Details and Security Vulnerabilities

📦

@swc/core

1.1.31

Comparision Betweeen 1.1.31 and 1.1.30

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

335.58 KB

328.52 KB

Version 1.1.31 Details

Version 1.1.31 of @swc/core, a super-fast alternative to Babel, was released on March 1st, 2020, following version 1.1.30 released on February 29th, 2020. Both versions share the same core dependencies including mkdirp, progress, node-fetch, and true-case-path, essential for file system operations, progress tracking, network requests, and accurate path resolution, respectively. Also, both versions share the same devDependencies including jest for testing, lodash for utility functions, neon-cli for Neon-related tasks, source-map for debugging, and typescript support, alongside a suite of Babel-related tools and plugins. This robust set of development dependencies ensures comprehensive testing, streamlined development, and compatibility with various JavaScript and TypeScript features, including decorators, class properties, and object rest/spread syntax.

The key difference lies in the dist section. Version 1.1.31 has a slightly larger unpacked size (343637 bytes) and file count (59) compared to version 1.1.30 (336402 bytes and 57 files respectively). This suggests that version 1.1.31 includes some new features, optimizations, or bug fixes that were not present in 1.1.30. While the changelog isn't provided, developers upgrading to 1.1.31 can anticipate a potentially more refined and feature-rich experience, benefiting from the included "under the hood" improvements. This package is MIT licensed and is part of the swc project, which can be found on Github.

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.