Version Details and Security Vulnerabilities

📦

@types/yargs

17.0.8

Comparision Betweeen 17.0.8 and 17.0.7

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

104.63 KB

54.82 KB

Version 17.0.8 Details

@types/yargs version 17.0.8 represents a incremental update to the TypeScript definitions for the popular yargs command-line argument parser library. Released on December 23, 2021, it follows version 17.0.7, which was published a month earlier on November 18, 2021. Both versions share the same core purpose: providing accurate and up-to-date TypeScript typings to enhance the development experience when working with yargs in TypeScript projects. This allows developers to leverage features like autocompletion, type checking, and improved code maintainability. The vital dependency on @types/yargs-parser remains consistent across both releases, ensuring compatibility with the underlying argument parsing logic.

A key change between the two versions lies in the distribution package size. Version 17.0.8 has a larger unpacked size of 107140 bytes and encompasses 10 files compared to version 17.0.7's 56136 bytes across 8 files. This increase in size likely reflects additions or refinements to the type definitions, possibly including improved coverage for specific yargs features, bug fixes related to type accuracy or support for newer yargs versions. Developers upgrading from 17.0.7 should be aware of this larger footprint, though the benefits of enhanced type safety and potentially better compatibility with newer yargs versions probably outweigh this. The MIT license and the location of the source code in the DefinitelyTyped repository remain the same.

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.