Eslint-plugin-expect-type has released version 0.4.1, a minor update from the previous stable version 0.4.0, designed to enhance your TypeScript ESLint experience. Both versions provide an intuitive way to assert TypeScript types within your code using special comments like ^? Twoslash, $ExpectError, and $ExpectType, aiding in documentation and preventing regressions.
Key improvements come primarily in the form of updated dev dependencies. The new version upgrades eslint-plugin-n from v16.3.1 to v17.0.0 and @typescript-eslint/utils bumps its minimum required version from '^6.10.0 || ^7.0.1' to '^6.10.0 || ^7.0.1' and also includes version ^7.4.0 in devDependencies but not in dependencies. npm-package-json-lint increases from v7.1.0 to v8.0.0, eslint-plugin-deprecation rises from v2.0.0 to v3.0.0 allowing for better and more robust linting using updated rules with the latest tools. Similarly, you will see slight changes to eslint-plugin-eslint-plugin moving from v5.0.6 to v6.0.0. Additionally, markdownlint-cli is updated from v0.39.0 to v0.41.0 and eslint-plugin-vitest is bumped from 0.3.9 to 0.4.0.
For developers, these changes mean a more reliable development environment; they should experience smoother usage with the latest ESLint and TypeScript tooling. The core functionality of expect-type remains consistent: ensuring type assertions within comments work as expected, catching type errors early, and improving overall code quality. Version 0.4.1 primarily focuses on refining the underlying tooling to ensure it keeps pace with the evolving JavaScript and TypeScript ecosystems.
The are not vulnerabilities for the version 0.4.1 of the package eslint-plugin-expect-type
