chore(deps): update eslint and prettier (minor)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint (source)	^9.11.1 -> ^9.16.0
eslint-plugin-import-x	^4.4.3 -> ^4.5.0
eslint-plugin-n	^17.10.3 -> ^17.14.0
eslint-plugin-react	^7.36.1 -> ^7.37.2
prettier (source)	^3.3.3 -> ^3.4.1

---

Release Notes

eslint/eslint (eslint)

v9.16.0

Compare Source

Features

• 8f70eb1 feat: Add ignoreComputedKeys option in sort-keys rule (#​19162) (Milos Djermanovic)

Documentation

• 9eefc8f docs: fix typos in use-isnan (#​19190) (루밀LuMir)
• 0c8cea8 docs: switch the order of words in no-unreachable (#​19189) (루밀LuMir)
• 0c19417 docs: add missing backtick to no-async-promise-executor (#​19188) (루밀LuMir)
• 8df9276 docs: add backtick in -0 in description of no-compare-neg-zero (#​19186) (루밀LuMir)
• 7e16e3f docs: fix caseSensitive option's title of sort-keys (#​19183) (Tanuj Kanti)
• 0c6b842 docs: fix typos in migration-guide.md (#​19180) (루밀LuMir)
• 353266e docs: fix a typo in debug.md (#​19179) (루밀LuMir)
• 5ff318a docs: delete unnecessary horizontal rule(---) in nodejs-api (#​19175) (루밀LuMir)
• 576bcc5 docs: mark more rules as handled by TypeScript (#​19164) (Tanuj Kanti)
• 742d054 docs: note that no-restricted-syntax can be used with any language (#​19148) (Milos Djermanovic)

Chores

• feb703b chore: upgrade to @eslint/js@9.16.0 (#​19195) (Francesco Trotta)
• df9bf95 chore: package.json update for @​eslint/js release (Jenkins)
• f831893 chore: add type for ignoreComputedKeys option of sort-keys (#​19184) (Tanuj Kanti)
• 3afb8a1 chore: update dependency @​eslint/json to ^0.8.0 (#​19177) (Milos Djermanovic)
• 1f77c53 chore: add repository.directory property to package.json (#​19165) (루밀LuMir)
• d460594 chore: update dependency @​arethetypeswrong/cli to ^0.17.0 (#​19147) (renovate[bot])
• 45cd4ea refactor: update default options in rules (#​19136) (Milos Djermanovic)

v9.15.0

Compare Source

v9.14.0

Compare Source

v9.13.0

Compare Source

v9.12.0

Compare Source

Features

• 5a6a053 feat: update to jiti v2 (#​18954) (Arya Emami)
• 17a07fb feat: Hooks for test cases (RuleTester) (#​18771) (Anna Bocharova)
• 2ff0e51 feat: Implement alternate config lookup (#​18742) (Nicholas C. Zakas)
• 2d17453 feat: Implement modified cyclomatic complexity (#​18896) (Dmitry Pashkevich)

Bug Fixes

• ea380ca fix: Upgrade retry to avoid EMFILE errors (#​18986) (Nicholas C. Zakas)
• fdd6319 fix: Issues with type definitions (#​18940) (Arya Emami)

Documentation

• ecbd522 docs: Mention code explorer (#​18978) (Nicholas C. Zakas)
• 7ea4ecc docs: Clarifying the Use of Meta Objects (#​18697) (Amaresh S M)
• d3e4b2e docs: Clarify how to exclude .js files (#​18976) (Milos Djermanovic)
• 57232ff docs: Mention plugin-kit in language docs (#​18973) (Nicholas C. Zakas)
• b80ed00 docs: Update README (GitHub Actions Bot)
• cb69ab3 docs: Update README (GitHub Actions Bot)
• 7fb0d95 docs: Update README (GitHub Actions Bot)
• 493348a docs: Update README (GitHub Actions Bot)
• 87a582c docs: fix typo in id-match rule (#​18944) (Jay)

Chores

• 555aafd chore: upgrade to @eslint/js@9.12.0 (#​18987) (Francesco Trotta)
• 873ae60 chore: package.json update for @​eslint/js release (Jenkins)
• d0a5414 refactor: replace strip-ansi with native module (#​18982) (Cristopher)
• b827029 chore: Enable JSON5 linting (#​18979) (Milos Djermanovic)
• 8f55ca2 chore: Upgrade espree, eslint-visitor-keys, eslint-scope (#​18962) (Nicholas C. Zakas)
• c1a2725 chore: update dependency mocha to ^10.7.3 (#​18945) (Milos Djermanovic)

un-ts/eslint-plugin-import-x (eslint-plugin-import-x)

v4.5.0

Compare Source

Minor Changes

• #​192 fbf639b Thanks @​SukkaW! - The PR implements the new resolver design proposed in https://github.com/un-ts/eslint-plugin-import-x/issues/40#issuecomment-2381444266

For eslint-plugin-import-x users

Like the ESLint flat config allows you to use js objects (e.g. import and require) as ESLint plugins, the new eslint-plugin-import-x resolver settings allow you to use js objects as custom resolvers through the new setting import-x/resolver-next:

// eslint.config.js
import { createTsResolver } from '#custom-resolver';
const { createOxcResolver } = require('path/to/a/custom/resolver');

const resolverInstance = new ResolverFactory({});
const customResolverObject = {
  interfaceVersion: 3,
  name: 'my-custom-eslint-import-resolver',
  resolve(modPath, sourcePath) {
    const path = resolverInstance.resolve(modPath, sourcePath);
    if (path) {
      return {
        found: true,
        path
      };
    }

    return {
      found: false,
      path: null
    }
  };
};

module.exports = {
  settings: {
    // multiple resolvers
    'import-x/resolver-next': [
      customResolverObject,
      createTsResolver(enhancedResolverOptions),
      createOxcResolver(oxcOptions),
    ],
    // single resolver:
    'import-x/resolver-next': [createOxcResolver(oxcOptions)]
  }
}

The new import-x/resolver-next no longer accepts strings as the resolver, thus will not be compatible with the ESLint legacy config (a.k.a. .eslintrc). Those who are still using the ESLint legacy config should stick with import-x/resolver.

In the next major version of eslint-plugin-import-x (v5), we will rename the currently existing import-x/resolver to import-x/resolver-legacy (which allows the existing ESLint legacy config users to use their existing resolver settings), and import-x/resolver-next will become the new import-x/resolver. When ESLint v9 (the last ESLint version with ESLint legacy config support) reaches EOL in the future, we will remove import-x/resolver-legacy.

We have also made a few breaking changes to the new resolver API design, so you can't use existing custom resolvers directly with import-x/resolver-next:

// When migrating to `import-x/resolver-next`, you CAN'T use legacy versions of resolvers directly:
module.exports = {
  settings: {
    // THIS WON'T WORK, the resolver interface required for `import-x/resolver-next` is different.
    'import-x/resolver-next': [
       require('eslint-import-resolver-node'),
       require('eslint-import-resolver-webpack'),
       require('some-custom-resolver')
    ];
  }
}

For easier migration, the PR also introduces a compat utility importXResolverCompat that you can use in your eslint.config.js:

// eslint.config.js
import eslintPluginImportX, { importXResolverCompat } from 'eslint-plugin-import-x';
// or
const eslintPluginImportX = require('eslint-plugin-import-x');
const { importXResolverCompat } = eslintPluginImportX;

module.exports = {
  settings: {
    // THIS WILL WORK as you have wrapped the previous version of resolvers with the `importXResolverCompat`
    'import-x/resolver-next': [
       importXResolverCompat(require('eslint-import-resolver-node'), nodeResolveOptions),
       importXResolverCompat(require('eslint-import-resolver-webpack'), webpackResolveOptions),
       importXResolverCompat(require('some-custom-resolver'), { option1: true, option2: '' })
    ];
  }
}

For custom import resolver developers

This is the new API design of the resolver interface:

export interface NewResolver {
  interfaceVersion: 3;
  name?: string; // This will be included in the debug log
  resolve: (modulePath: string, sourceFile: string) => ResolvedResult;
}

// The `ResultNotFound` (returned when not resolved) is the same, no changes
export interface ResultNotFound {
  found: false;
  path?: undefined;
}

// The `ResultFound` (returned resolve result) is also the same, no changes
export interface ResultFound {
  found: true;
  path: string | null;
}

export type ResolvedResult = ResultNotFound | ResultFound;

You will be able to import NewResolver from eslint-plugin-import-x/types.

The most notable change is that eslint-plugin-import-x no longer passes the third argument (options) to the resolve function.

We encourage custom resolvers' authors to consume the options outside the actual resolve function implementation. You can export a factory function to accept the options, this factory function will then be called inside the eslint.config.js to get the actual resolver:

// custom-resolver.js
exports.createCustomResolver = (options) => {
  // The options are consumed outside the `resolve` function.
  const resolverInstance = new ResolverFactory(options);

  return {
    name: 'custom-resolver',
    interfaceVersion: 3,
    resolve(mod, source) {
      const found = resolverInstance.resolve(mod, {});

      // Of course, you still have access to the `options` variable here inside
      // the `resolve` function. That's the power of JavaScript Closures~
    }
  }
};

// eslint.config.js
const { createCustomResolver } = require('custom-resolver')

module.exports = {
  settings: {
    'import-x/resolver-next': [
       createCustomResolver(options)
    ];
  }
}

This allows you to create a reusable resolver instance to improve the performance. With the existing version of the resolver interface, because the options are passed to the resolver function, you will have to create a resolver instance every time the resolve function is called:

module.exports = {
  interfaceVersion: 2,
  resolve(mod, source) {
    // every time the `resolve` function is called, a new instance is created
    // This is very slow
    const resolverInstance = ResolverFactory.createResolver({});
    const found = resolverInstance.resolve(mod, {});
  },
};

With the factory function pattern, you can create a resolver instance beforehand:

exports.createCustomResolver = (options) => {
  // `enhance-resolve` allows you to create a reusable instance:
  const resolverInstance = ResolverFactory.createResolver({});
  const resolverInstance = enhanceResolve.create({});

  // `oxc-resolver` also allows you to create a reusable instance:
  const resolverInstance = new ResolverFactory({});

  return {
    name: "custom-resolver",
    interfaceVersion: 3,
    resolve(mod, source) {
      // the same re-usable instance is shared across `resolve` invocations.
      // more performant
      const found = resolverInstance.resolve(mod, {});
    },
  };
};

Patch Changes

• #​184 bc4de89 Thanks @​marcalexiei! - fix(no-cycle): improves the type declaration of the rule no-cycle’s maxDepth option

• #​184 bc4de89 Thanks @​marcalexiei! - fix(first): improves the type declaration of the rule first's option

• #​184 bc4de89 Thanks @​marcalexiei! - fix(no-unused-modules): improves the type declaration of the rule no-unused-modules’s missingExports option

• #​184 bc4de89 Thanks @​marcalexiei! - fix(no-deprecated): improve error message when no description is available

eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.14.0

Compare Source

🌟 Features

• no-sync: Add ignores option (#​386) (c8fbf00)
• no-unsupported: support Node 23.2.0 & 23.3.0 (#​390) (a52c968)

v17.13.2

Compare Source

🩹 Fixes

• no-missing-require: handle multiple resolvePaths (#​383) (df6ad2a)

v17.13.1

Compare Source

🩹 Fixes

• exported / referenced plugin same instance (#​380) (3c45b67)

v17.13.0

Compare Source

🌟 Features

• no-unsupported: support Node 20.18.0 (#​374) (d39d99a)

🩹 Fixes

• no-unsupported: fix node:test module (#​378) (0b228dd)

🧹 Chores

• update dependencies (#​375) (8a8104e)

v17.12.0

Compare Source

🌟 Features

• no-unsupported: Support node 23.0.0 and 22.10.0 (#​358) (0fd0350)
• no-unsupported: Support node 23.1.0 (#​370) (06d60ae)

🩹 Fixes

• no-unsupported: getCallSite is experimental (#​363) (d15c63a)
• no-unsupported: support missing process.features (#​362) (9552a4a)
• update dependencies (#​365) (bf34ca5)

🧹 Chores

• Improve typescript types and strictness (#​367) (18cdd53)

v17.11.1

Compare Source

🩹 Fixes

• no-deprecated-api: dedeprecate process.nextTick (#​350) (dd889ab)

v17.11.0

Compare Source

🌟 Features

• no-missing-import: Add ignoreTypeImport options (#​344) (e022aba)
• no-process-env: Allow users to exclude specific variables (#​345) (b16a475)
• Update no-unsupported to node v22.9.0 (#​342) (87fb484)

🩹 Fixes

• no-missing-import: Ignore node builtins in package.json imports (#​346) (148e47e)
• no-missing-import: Resolve tsconfig paths relative to the tsconfig (#​343) (6cd7954)

📚 Documentation

• Explain the transitive dependency case for no-extraneous-* (#​347) (8c0a2cc)

jsx-eslint/eslint-plugin-react (eslint-plugin-react)

v7.37.2

Compare Source

Fixed

• [destructuring-assignment]: fix false negative when using typeof props.a (#​3835 @​golopot)

Changed

• [Refactor] [destructuring-assignment]: use getParentStatelessComponent (#​3835 @​golopot)

v7.37.1

Compare Source

Fixed

• [meta] do not npmignore d.ts files (#​3836 @​ljharb)

Changed

• [readme] Fix shared settings link (#​3834 @​MgenGlder)

v7.37.0

Compare Source

Added

• add type generation (#​3830 @​voxpelli)
• [no-unescaped-entities]: add suggestions (#​3831 @​StyleShit)
• [forbid-component-props]: add allowedForPatterns/disallowedForPatterns options (#​3805 @​Efimenko)
• [no-unstable-nested-components]: add propNamePattern to support custom render prop naming conventions (#​3826 @​danreeves)

Changed

• [readme] flat config example for react 17+ (#​3824 @​GabenGar)

prettier/prettier (prettier)

v3.4.1

Compare Source

diff

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)

<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

v3.4.0

Compare Source

diff

🔗 Release Notes

---

Configuration

📅 Schedule: Branch creation - "after 9pm,before 9am" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.