Version Details and Security Vulnerabilities

📦

retext-sentence-spacing

6.0.0

Comparision Betweeen 6.0.0 and 5.2.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

12.98 KB

11.52 KB

Version 6.0.0 Details

Retext-sentence-spacing has a new major version, 6.0.0, released in September 2023, succeeding version 5.2.0 from December 2021. This update brings several changes relevant to developers using the library.

One notable difference lies in the dependencies. Version 6.0.0 updates @types/nlcst, nlcst-to-string, and unist-util-visit to newer major versions. It also introduces vfile as a direct dependency. Consequently, @types/unist and unified dependencies were removed. These changes likely reflect internal refactoring and alignment with the latest versions of the underlying natural language processing (NLP) ecosystem components.

The development dependencies also saw significant updates. Version 6.0.0 embraces newer tools: it uses @types/node version 20, c8 version 8, prettier version 3, remark-cli version 11, retext version 9, typescript version 5, and xo version 0.56. Conversely, version 5.2.0 relied on older versions of these tools like @types/node (implicit through other dependencies), c8 version 7, prettier version 2, remark-cli version 10, retext version 8, typescript version 4 and xo version 0.47. The removal of rimraf and tape in version 6.0.0 suggests a shift in testing methodologies, possibly leveraging c8's built-in capabilities.

The unpacked size of version 6.0.0 is slightly larger (13295 bytes) compared to version 5.2.0 (11801 bytes), potentially due to the new dependencies or changes in the codebase. Upgrading to version 6.0.0 ensures compatibility with recent tooling and best practices in the retext ecosystem, but developers should carefully review the breaking changes from the major version updates of dependencies like @types/nlcst and ensure their code remains compatible.

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.