Version Details and Security Vulnerabilities

📦

midnight-smoker

2.0.4

Comparision Betweeen 2.0.4 and 2.0.3

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

52.6 KB

Version 2.0.4 Details

Midnight Smoker, a tool designed to run smoke tests against packages as they would be published, has released version 2.0.4, following closely on the heels of version 2.0.3. While both versions share the same core functionality and many dependencies, a few key upgrades in 2.0.4 make it a worthwhile update for developers.

The most notable changes are found in the dependency updates. Specifically, "yargs" has been bumped from version 17.7.1 to 17.7.2, and "which" has been updated from 3.0.0 to 3.0.1. Development dependencies have also seen revisions - "@commitlint/cli" and "@commitlint/config-conventional" updated from 17.6.1 to 17.6.3, "eslint" from 8.38.0 to 8.40.0, markdownlint-cli2" to 0.7.1 from 0.6.0 and "sinon" from 15.0.3 to 15.1.0. Additionally, the type definition for Node.js, "@types/node," has been updated from version 18.15.11 to 18.16.13. Lint-staged experienced an update from 13.2.1 to 13.2.2, and the Prettier package upgraded from 2.8.7 to 2.8.8.

These updates likely incorporate bug fixes, performance improvements, and potentially new features within those individual packages that Midnight Smoker relies upon. For developers, upgrading to 2.0.4 ensures they are leveraging the most up-to-date and stable versions of these underlying tools, which could lead to a smoother smoke testing experience. While seemingly minor, these incremental improvements contribute to the overall robustness and reliability of Midnight Smoker in verifying package publish readiness.

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.