build(deps): bump eslint-plugin-import-x from 3.1.0 to 4.6.1

[dependabot]

Bumps eslint-plugin-import-x from 3.1.0 to 4.6.1.

Release notes

Sourced from eslint-plugin-import-x's releases.

v4.6.1

Patch Changes

• #211 be9c3e8 Thanks @​mrginglymus! - Fix enhanced-resolve dependency

v4.6.0

Minor Changes

• #209 46d2360 Thanks @​SukkaW! - When eslint-plugin-import-x was forked from eslint-plugin-import, we copied over the default resolver (which is eslint-import-resolver-node) as well. However, this resolver doesn't supports exports in the package.json file, and the current maintainer of the eslint-import-resolver-node (ljharb) doesn't have the time implementing this feature and he locked the issue import-js/eslint-plugin-import#1810.

  So we decided to implement our own resolver that "just works". The new resolver is built upon the enhanced-resolve that implements the full Node.js Resolver Algorithm. The new resolver only implements the import resolver interface v3, which means you can only use it with ESLint Flat config. For more details about the import resolver interface v3, please check out #192.

  In the next major version of eslint-plugin-import-x, we will remove the eslint-import-resolver-node and use this new resolver by default. In the meantime, you can try out this new resolver by setting the import-x/resolver-next option in your eslint.config.js file:

  // eslint.config.js
  const eslintPluginImportX = require('eslint-plugin-import-x');
  const { createNodeResolver } = eslintPluginImportX;
  module.exports = {
  plugins: {
  'import-x': eslintPluginImportX,
  },
  settings: {
  'import-x/resolver-next': [
  // This is the new resolver we are introducing
  createNodeResolver({
  /**
  * The allowed extensions the resolver will attempt to find when resolving a module
  * By default it uses a relaxed extension list to search for both ESM and CJS modules
  * You can customize this list to fit your needs
  *
  * @​default ['.mjs', '.cjs', '.js', '.json', '.node']
  /
  extensions?: string[];
  /*
  * Optional, the import conditions the resolver will used when reading the exports map from "package.json"
  * By default it uses a relaxed condition list to search for both ESM and CJS modules
  * You can customize this list to fit your needs
  *
  * @​default ['default', 'module', 'import', 'require']
  /
  conditions: ['default', 'module', 'import', 'require'],
  // You can pass more options here, see the enhanced-resolve documentation for more details
  // https://github.com/webpack/enhanced-resolve/tree/v5.17.1?tab=readme-ov-file#resolver-options
  }),
  // you can add more resolvers down below
  require('eslint-import-resolver-typescript').createTypeScriptImportResolver(
  /* options of eslint-import-resolver-typescript */

... (truncated)

Changelog

Sourced from eslint-plugin-import-x's changelog.

4.6.1

Patch Changes

• #211 be9c3e8 Thanks @​mrginglymus! - Fix enhanced-resolve dependency

4.6.0

Minor Changes

• #209 46d2360 Thanks @​SukkaW! - When eslint-plugin-import-x was forked from eslint-plugin-import, we copied over the default resolver (which is eslint-import-resolver-node) as well. However, this resolver doesn't supports exports in the package.json file, and the current maintainer of the eslint-import-resolver-node (ljharb) doesn't have the time implementing this feature and he locked the issue import-js/eslint-plugin-import#1810.

  So we decided to implement our own resolver that "just works". The new resolver is built upon the enhanced-resolve that implements the full Node.js Resolver Algorithm. The new resolver only implements the import resolver interface v3, which means you can only use it with ESLint Flat config. For more details about the import resolver interface v3, please check out #192.

  In the next major version of eslint-plugin-import-x, we will remove the eslint-import-resolver-node and use this new resolver by default. In the meantime, you can try out this new resolver by setting the import-x/resolver-next option in your eslint.config.js file:

  // eslint.config.js
  const eslintPluginImportX = require('eslint-plugin-import-x');
  const { createNodeResolver } = eslintPluginImportX;
  module.exports = {
  plugins: {
  'import-x': eslintPluginImportX,
  },
  settings: {
  'import-x/resolver-next': [
  // This is the new resolver we are introducing
  createNodeResolver({
  /**
  * The allowed extensions the resolver will attempt to find when resolving a module
  * By default it uses a relaxed extension list to search for both ESM and CJS modules
  * You can customize this list to fit your needs
  *
  * @​default ['.mjs', '.cjs', '.js', '.json', '.node']
  /
  extensions?: string[];
  /*
  * Optional, the import conditions the resolver will used when reading the exports map from "package.json"
  * By default it uses a relaxed condition list to search for both ESM and CJS modules
  * You can customize this list to fit your needs
  *
  * @​default ['default', 'module', 'import', 'require']
  */
  conditions: ['default', 'module', 'import', 'require'],
  // You can pass more options here, see the enhanced-resolve documentation for more details
  // https://github.com/webpack/enhanced-resolve/tree/v5.17.1?tab=readme-ov-file#resolver-options
  }),
  // you can add more resolvers down below
  require('eslint-import-resolver-typescript').createTypeScriptImportResolver(

... (truncated)

Commits

• 1ff90b8 chore: release eslint-plugin-import-x (#213)
• be9c3e8 fix: move enhanced-resolve to prod deps (#211)
• c3950d4 chore: release eslint-plugin-import-x (#207)
• 46d2360 feat: implement a resolver that supports exports (#209)
• 449738f fix(no-duplicates): autofix insert type prefix without new line (#206)
• af711e5 chore: release eslint-plugin-import-x (#202)
• 32e9b55 fix(no-duplicates): merge type import as with value import (#204)
• ac6d2e1 fix: include @types/doctrine to dependencies (#198)
• f22eaa9 chore: release eslint-plugin-import-x (#190)
• 739e22c chore: fix changeset (#193)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)