@endo/eslint-plugin@3.0.0
Major Changes
-
#3319
e352f0fThanks @boneskull! - Breaking: Backwards compatibility with legacy ESLint config files is provided on a best-effort basis, given ESLint's deprecation of rules and third-party replacements. Recommended rules from ESLint 9+ have also been configured.Breaking: Minimum supported Node.js version is now v22.12.0.
Breaking:
@jessie.js/eslint-pluginis no longer a dependency of@endo/eslint-plugin. This removes a cyclic dependency (@jessie.js/eslint-plugindepends on@endo/eslint-plugin, and vice versa).eslint-plugin-unicornis no longer a peer dependency of@endo/eslint-pluginand can be safely removed from yourdevDependencies(unless you consume it directly, of course).- The
flat/recommendedconfig no longer registers the@jessie.jsplugin, applies@jessie.js/safe-await-separator, or installs theuse-jessieprocessor. The legacyrecommendedandinternalconfigs likewise no longer extendplugin:@jessie.js/recommendedor set the@jessie.js/use-jessieprocessor. See "Migration" below for more details. - New rules have been added from
@eslint/js'recommendedconfiguration, includingno-assign-to-exported-let-var-or-functionandno-harden-pattern-maker, which may or may not already be handled by your existing configuration.
Migration: Consumers that rely on the rules and processor provided by
@jessie.js/eslint-pluginmust install@jessie.js/eslint-pluginmanually and wire it up alongside@endo/eslint-plugin:import jessie from '@jessie.js/eslint-plugin'; import endo from '@endo/eslint-plugin'; export default [ ...endo.configs['flat/recommended'], ...jessie.configs['flat/recommended'], { processor: jessie.processors['use-jessie'] }, ];
Furthermore, the new rules will need to be addressed as appropriate for your project.
-
#3325
ac72fcaThanks @boneskull! - Certain tags are no longer allowed by ourjsdoc/check-tag-namesrule configuration, including@code.The new rules
jsdoc/reject-any-typeandjsdoc/ts-no-empty-object-typehave been disabled.
Patch Changes
- #3305
6d6160dThanks @turadg! - Republish with resolved dependency versions. The 2.6.0 manifest on npm shippedcatalog:protocol specifiers foreslint-plugin-importandtypescript, which npm cannot resolve; the publish toolchain now resolves thecatalog:protocol to concrete version ranges at pack time. Fixes #3304.