Version Details and Security Vulnerabilities

📦

@microsoft/api-extractor

7.52.11

Comparision Betweeen 7.52.11 and 7.52.10

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

204

Unpacked Size

1.92 MB

Version 7.52.11 Details

Version 7.52.11 of @microsoft/api-extractor builds upon the solid foundation of 7.52.10, offering refinements to this essential tool for TypeScript library developers. Both versions empower developers to analyze their exported APIs, generate comprehensive documentation, and create optimized .d.ts rollups. Key dependencies like typescript, semver, lodash, @microsoft/tsdoc, and @rushstack/* libraries remain consistent, ensuring compatibility and stability. The core functionality for API analysis and documentation generation is unchanged, providing a seamless upgrade path for existing users.

One notable difference in version 7.52.11 is the inclusion of @microsoft/api-extractor-model as a direct dependency during its build. This suggests tighter integration or potential updates to the API extractor's internal model representation. This may result in small improvements in the data extraction or validation processes, although its is hard to identify directly. The unpacked size also slightly increased by ~2KB.

Developers leveraging @microsoft/api-extractor can expect reliable API validation, generation of API reports for review, and automated creation of polished documentation. This package remains crucial for maintaining API quality and consistency across TypeScript libraries, helping to ensure a smooth experience for consumers of your code. Given similarities, the upgrade from 7.52.10 to 7.52.11 should be straightforward.

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.