Version Details and Security Vulnerabilities

📦

stylelint-config-standard

30.0.0

Comparision Betweeen 30.0.0 and 29.0.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

8.28 KB

18.7 KB

Version 30.0.0 Details

Stylelint-config-standard version 30.0.0 brings notable updates for developers utilizing Stylelint for CSS linting. A core change is the upgrade of its dependency, stylelint-config-recommended, moving from version 9.0.0 to version 10.0.0, likely incorporating new and updated recommended rules. Crucially, the peer dependency stylelint itself is bumped from version ^14.14.0 to ^15.0.0, signaling potential compatibility considerations; developers upgrading should ensure their projects are compatible with Stylelint v15.

The development environment surrounding the package also sees several updates. jest jumps from v28.1.3 to v29.4.2, reflecting advancements in testing capabilities. eslint goes from v8.25.0 to v8.33.0, and prettier from v2.7.1 to v2.8.4, pointing to more enhanced code formatting and linting during development. husky also sees an update from 8.0.1 to 8.0.3. Surprisingly, the unpacked size is significantly reduced in the newer version, from 19145 to 8478, indicating potential optimizations in the package structure or removal of unnecessary files. The release date confirms a more recent update in February 2023 compared to October 2022 for version 29.0.0. Developers adopting v30.0.0 can anticipate refined linting rules and an updated development toolchain, but should verify their Stylelint setup for smooth integration with the latest major version. All the other dev dependencies remains on the same major version.

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.