Version Details and Security Vulnerabilities

📦

eslint-plugin-expect-type

0.3.0

Comparision Betweeen 0.3.0 and 0.2.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

149.13 KB

39.34 KB

Version 0.3.0 Details

eslint-plugin-expect-type has seen significant updates between version 0.2.3 and 0.3.0, reflecting a commitment to modernizing the developer experience and expanding its feature set. The newer version boasts enhanced support for ESLint and TypeScript, evident from the updated peer dependencies; it now requires ESLint version 7 or higher, TypeScript version 4 or greater, and @typescript-eslint/parser version 6 or above. This ensures compatibility with the latest language features and tooling improvements.

A notable difference lies in the dependencies. Version 0.3.0 upgrades @typescript-eslint/utils to version 6.10.0 and fs-extra to 11.1.1, while dropping jest and ts-jest and introducing vitest for testing. This indicates a shift towards a more modern testing framework and potentially better integration with contemporary TypeScript projects using modules. The proliferation of devDependencies in version 0.3.0 also suggests improved tooling around development, linting, and formatting, with packages like knip, cspell, prettier, eslint-plugin-jsdoc, and many others ensuring code quality and consistency. Version 0.3.0 includes eslint-doc-generator to quickly maintain documentation as the project evolves.

For developers, these changes translate to better support for modern JavaScript and TypeScript features, a more robust testing environment, and enhanced code quality and maintainability. The expanded dev dependencies provide a smoother and more automated development workflow, reducing the likelihood of errors and improving the overall developer experience. These upgrades establish eslint-plugin-expect-type as a more reliable and feature-rich tool for type assertion within ESLint, and indicate improved maintainability, stability, and integration with current toolchains.

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.