Version Details and Security Vulnerabilities

📦

marked-man

1.3.6

Comparision Betweeen 1.3.6 and 1.3.5

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

12.55 KB

13.92 KB

Version 1.3.6 Details

Marked-man provides a convenient way to generate man pages directly from Markdown files, leveraging the popular marked library for Markdown parsing. Both version 1.3.6 and the preceding stable version 1.3.5 offer this functionality, acting as wrappers that streamline the creation of man page documentation, inspired by the principles of ronn. They share core dependencies like marked (version ^4.2.12) and read-pkg-up (version ^9.1.0), ensuring compatibility with recent Markdown features and package information retrieval. The development dependencies, specifically @kapouer/eslint-config (version ^1.9.0), remain consistent, indicating adherence to coding style guidelines.

The key difference lies in the release timeline and subtle internal changes. Version 1.3.6 was released on April 17, 2024, whereas version 1.3.5 was released much earlier on December 14, 2023. The dist object reveals that version 1.3.6 has a slightly smaller unpacked size (12856 bytes) and fewer files (9) compared to version 1.3.5 (14257 bytes and 10 files), suggesting potential optimizations or refactoring within the package. While the core functionality remains the same, developers upgrading to 1.3.6 might experience slightly improved performance or a smaller footprint. For users already benefiting from marked-man, the upgrade offers a potentially refined experience. For newcomers, either version provides a solid foundation for building man pages from Markdown documents, simplifying documentation workflows.

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.