fix(deps): update dependency eslint-plugin-import-x to v4.17.1 by renovate[bot] · Pull Request #425 · cpsoinos/config

renovate · 2024-08-26T22:30:00Z

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-import-x	`4.4.3` → `4.17.1`
eslint-plugin-import-x	`^3.1.0` → `^4.0.0`

Release Notes

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

`v4.17.1`

Compare Source

Patch Changes

#498 cf25a01 Thanks @marcalexiei! - fix(extensions): don't require an extension for package subpaths that resolve to a .d.ts (e.g. vitest/config)

`v4.17.0`

Compare Source

Minor Changes

#474 4b2c0c5 Thanks @regseb! - Support RegExp in the import-x/ignore setting and the ignore option of the no-unresolved rule.

Patch Changes

#494 1c84235 Thanks @morgan-coded! - Fixed no-unresolved crashing when case-sensitive path checks encounter EACCES or EPERM on an ancestor directory.
#481 3e13121 Thanks @B4nan! - fix: memoize legacyNodeResolve resolver to avoid native memory leak
#484 9a07009 Thanks @sairus2k! - Make the extensions rule check Node.js subpath imports (specifiers starting with #, e.g. #utils/helper). Previously parsePath treated a leading # as a URL hash fragment, so the rule skipped extension validation for these imports.

Note: single-segment subpath imports without a slash (e.g. #dep) are still skipped by the existing external-root-module classification; fixing that is deferred to avoid expanding scope.
#468 240ed58 Thanks @silverwind! - Make extensions handle .d.ts correctly
#479 e3cc7e4 Thanks @mrginglymus! - fix: strip querystrings and hash fragments when checking for file existence
#476 fce29b1 Thanks @nbouvrette! - fix(deps): replace @package-json/types with an inline minimal type

`v4.16.2`

Compare Source

Patch Changes

#457 1da4043 Thanks @SukkaW! - Make the no-unused-modules rule no-op on ESLint 10 or later for now before we can implement an alternative. A warning message about this behavior is added, and can be suppressed with the new suppressMissingFileEnumeratorAPIWarning rule option (import-x/no-unused-modules: ['error', { suppressMissingFileEnumeratorAPIWarning: true }]).
#450 a51be0f Thanks @andrewgaun! - fix(deps): Bumping minimatch 10 version to avoid dependency with a critical vulnerability

Updating the minimum minimatch 10 version to 10.1.2 which updates a dependency (@isaacs/brace-expansion) with a critical vulnerability. See GHSA-7h2j-956f-4vf2
#466 b669aca Thanks @SukkaW! - Make eslint-plugin-import-x compatible with ESLint's defineConfig
#434 a3aae61 Thanks @stepankuzmin! - fix(deps): replace type-fest with @package-json/types

PackageJson types are imported in published declaration files (lib/rules/no-extraneous-dependencies.d.ts and lib/utils/read-pkg-up.d.ts), which causes TypeScript compilation errors for consumers who don't have skipLibCheck enabled. Replacing type-fest with the smaller @package-json/types package ensures the types are available to all consumers while reducing bundle size.
#458 60312ee Thanks @SukkaW! - Bump peer deps version range to include ESLint 10 support
#443 b416a8a Thanks @baevm! - consistent-type-specifier-style: Add exception for TS resolution-mode import attributes
#454 d3f8d67 Thanks @SukkaW! - First step toward ESLint 10 support:
- sourceType determination now prefers context.languageOptions when possible
- Ensure context.parserOptions no longer results in crashes with ESLint 10
- Merge getParser and getParserPath implementations into one getParserOrPath
#406 d0a7816 Thanks @marcalexiei! - fix(package): remove config and rules exports pointing to empty files

`v4.16.1`

Compare Source

Patch Changes

#399 33f07b4 Thanks @JounQin! - fix: should only use context.physicalFilename as fallback instead of main source
#400 34adb40 Thanks @renovate! - chore(deps): bump stable-hash-x v0.2

`v4.16.0`

Compare Source

Minor Changes

#386 1c8b9ae Thanks @Rel1cx and @JounQin! - feat: port react-x/prefer-react-namespace-import into prefer-namespace-import

Patch Changes

#393 14cb948 Thanks @lnhrdt and @JounQin! - fix(extensions): always calculate fix option
#388 1089d9f Thanks @JounQin! - fix: take context.cwd into account for cache key
#390 8ca9272 Thanks @JounQin, @scytacki and @arcanis! - fix: pnp issue when used in a monorepo

`v4.15.2`

Compare Source

Patch Changes

#378 cdb95ba Thanks @error-four-o-four! - chore: adopt new deprecated: DeprecatedInfo meta rule option
#383 738a7cf Thanks @JounQin! - fix: get npm client and install command correctly
#382 d536756 Thanks @JounQin! - chore: bump unrs-resolver to v1.9.0, it'll fallback to napi-postinstall check at runtime

`v4.15.1`

Compare Source

Patch Changes

#373 90ec1f1 Thanks @JounQin! - chore: migrate stable-hash to stable-hash-x
#371 4f97a1a Thanks @dword-design and @JounQin! - fix: take context.cwd into account for glob options of rules no-extraneous-dependencies and no-unassigned-import
#371 4f97a1a Thanks @JounQin! - fix: enable nocomment: true for glob options of rules no-import-module-exports and no-namespace
#368 74a16c5 Thanks @JoseGoncalves! - fix: drop languageOptions config from flat/recommended

Patch Changes

#360 3a3f5f8 Thanks @JounQin! - fix: try/catch enumerator.iterateFiles gracefully
#357 46c8bc6 Thanks @JounQin! - chore(deps): bump @typescript-eslint/utils and unrs-resolver

`v4.14.1`

Compare Source

Patch Changes

#355 81f3d31 Thanks @JounQin! - fix: tslib is no longer used because we're targeting ES2022

`v4.14.0`

Compare Source

Minor Changes

#272 43cdd21 Thanks @SukkaW and @JounQin! - feat: map legacy node resolver to the new one with fallback support
#350 12a7cda Thanks @43081j! - Expose flat configs in configs object to allow use of ESLint extends

Patch Changes

#352 3bc48fc Thanks @JounQin! - fix: enable nocomment glob option for rule no-unassigned-import's allow option

`v4.13.3`

Compare Source

Patch Changes

#348 f949929 Thanks @JounQin! - fix(types): exported importX should also have flatConfigs as property

`v4.13.2`

Compare Source

Patch Changes

#344 2c007d0 Thanks @JounQin! - fix: share same plugin reference for default export
#346 2991f2e Thanks @JounQin! - fix: rule dynamic-import-chunkname crash due to ts migration
#342 a55dcc7 Thanks @JounQin! - fix(deps): bump eslint-import-context to v0.1.5

`v4.13.1`

Compare Source

Patch Changes

#340 180785d Thanks @JounQin! - fix(deps): bump eslint-import-context to v0.1.4

`v4.13.0`

Compare Source

Minor Changes

#335 371ebee Thanks @JounQin! - feat: integrate eslint-import-context to get rule context without additional params

`v4.12.2`

Compare Source

Patch Changes

#332 0b3809b Thanks @JounQin! - fix: remove buggy module-sync exports field

`v4.12.1`

Compare Source

Patch Changes

#329 4b284cb Thanks @JounQin! - feat: add suggestions support for extensions unexpected case

`v4.12.0`

Compare Source

Minor Changes

#327 90c1cd0 Thanks @JounQin! - feat(extensions): support pathGroupOverrides and fix options

`v4.11.1`

Compare Source

Patch Changes

#321 fc4c72c Thanks @SukkaW! - fix: accept non-array resolver in resolver-next setting

`v4.11.0`

Compare Source

Minor Changes

#314 11ebfbd Thanks @JounQin! - refactor: migrate deprecated doctrine to comment-parser

`v4.10.6`

Compare Source

Patch Changes

#310 d54302f Thanks @JounQin! - chore: bump unrs-resolver to v1.6.0

`v4.10.5`

Compare Source

Patch Changes

#300 db1824b Thanks @JounQin! - fix: support run with worker eval

`v4.10.4`

Compare Source

Patch Changes

#299 bf50a4d Thanks @renovate! - chore(deps): bump @typescript-eslint/utils to v8.30
#297 9769f3c Thanks @JounQin! - fix: support run with node --eval

`v4.10.3`

Compare Source

Patch Changes

#292 1342127 Thanks @JounQin! - refactor: remove unnecessary check for pnpapi because unrs-resolver already handles it

`v4.10.2`

Compare Source

Patch Changes

#282 9f4f213 Thanks @JounQin! - chore: bump unrs-resolver to v1.4.1

`v4.10.1`

Compare Source

Patch Changes

#280 4966857 Thanks @JounQin! - chore: bump all (dev) deps
#280 4966857 Thanks @JounQin! - fix: incorrect top level types field for cjs

`v4.10.0`

Compare Source

Minor Changes

#271 6cba8eb Thanks @JounQin! - feat: migrate to ESM primary

Patch Changes

#276 e52168e Thanks @jribbens! - fix: allow minimatch 9 or 10

`v4.9.4`

Compare Source

Patch Changes

#267 e9e2300 Thanks @JounQin! - chore: bump unrs-resolver to v1.3.3

`v4.9.3`

Compare Source

Patch Changes

#263 c0046a9 Thanks @JounQin! - chore: migrate to rebranding unrs-resolver with new targets supported:
- i686-pc-windows-msvc
- armv7-unknown-linux-musleabihf
- powerpc64le-unknown-linux-gnu
- s390x-unknown-linux-gnu

`v4.9.2`

Compare Source

Patch Changes

#259 baf7086 Thanks @JounQin! - fix: PluginConfig should use classic config

`v4.9.1`

Compare Source

Patch Changes

#256 e66575f Thanks @JounQin! - refactor: revert picomatch back to minimatch

`v4.9.0`

Compare Source

Minor Changes

#248 6940b14 Thanks @TrevorBurnham! - feat: port all order rule new options from upstream

`v4.8.1`

Compare Source

Patch Changes

#251 af5de32 Thanks @JounQin! - chore: bump rspack-resolver to v1.2.0

`v4.8.0`

Compare Source

Minor Changes

#240 60eb443 Thanks @JounQin! - feat: migrate minimatch to picomatch

`v4.7.2`

Compare Source

Patch Changes

#245 437db59 Thanks @JounQin! - fix: align pnpapi resolved path with enhanced-resolve

`v4.7.1`

Compare Source

Patch Changes

#243 5bc8976 Thanks @JounQin! - fix: use rspack-resolver fork for pnp support

`v4.7.0`

Compare Source

Minor Changes

#237 53b316c Thanks @JounQin! - feat: migrate enhanced-resolve to oxc-resolver
#214 091d2da Thanks @mrginglymus! - Improve windows support

Patch Changes

#238 c8a388d Thanks @JounQin! - fix: change default conditions and mainFields

default should be last matched, module should be in mainFields.

Reference https://github.com/isaacs/resolve-import/blob/03daf0a9649d183bea40975a7777ae72955f44b8/src/resolve-conditional-value.ts#L15

`v4.6.1`

Compare Source

Patch Changes

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

`v4.6.0`

Compare Source

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
         *
         * @&#8203;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
         *
         * @&#8203;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 */
      )
    ],
  },
};

We do not plan to implement reading baseUrl and paths from the tsconfig.json file in this resolver. If you need this feature, please checkout eslint-import-resolver-typescript (also powered by enhanced-resolve), eslint-import-resolver-oxc (powered by oxc-resolver), eslint-import-resolver-next (also powered by oxc-resolver), or other similar resolvers.

Patch Changes

#206 449738f Thanks @privatenumber! - insert type prefix without new line

`v4.5.1`

Compare Source

Patch Changes

#198 ac6d2e1 Thanks @voxpelli! - Fix #197 with missing types
#204 32e9b55 Thanks @privatenumber! - fix type-import and value-import merging when import-as is used

`v4.5.0`

Compare Source

Minor Changes

#192 fbf639b Thanks @SukkaW! - The PR implements the new resolver design proposed in #40 (comment)

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.

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

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

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

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

changeset-bot · 2024-08-26T22:30:03Z

🦋 Changeset detected

Latest commit: 6d2223a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@cpsoinos/eslint-config-base	Patch
@cpsoinos/eslint-flat-configs	Patch
@cpsoinos/eslint-config-typescript	Patch
@cpsoinos/eslint-config-react-ts	Patch
@cpsoinos/eslint-config-vue-ts	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

nx-cloud · 2024-08-26T22:30:22Z

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 0d48728. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

✅ Successfully ran 2 targets

Sent with 💌 from NxCloud.

renovate Bot added the dependencies Pull requests that update a dependency file label Aug 26, 2024

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 3 times, most recently from 9dbf672 to eec7976 Compare September 9, 2024 21:44

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 3 times, most recently from 583aec0 to 475bbf7 Compare September 16, 2024 21:55

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 3 times, most recently from 4ca3185 to 1ae5256 Compare September 30, 2024 21:39

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 3 times, most recently from f25c064 to 6e1a91d Compare October 9, 2024 00:56

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 3 times, most recently from d5e8013 to 85f83a9 Compare October 17, 2024 21:57

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 3 times, most recently from 7197e6d to 2756435 Compare October 28, 2024 19:32

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 3 times, most recently from 479e865 to 74360e1 Compare November 4, 2024 22:16

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 2 times, most recently from 165ec16 to 63da3ad Compare November 18, 2024 21:24

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch 3 times, most recently from 5d97b13 to ed89ea4 Compare November 25, 2024 21:23

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from 0d48728 to 8582732 Compare November 30, 2024 21:07

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from 8faf346 to 207ef26 Compare March 15, 2025 21:54

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.7.0~~ fix(deps): update dependency eslint-plugin-import-x to v4.7.1 Mar 15, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from c3f04b8 to 5ca7713 Compare March 16, 2025 02:05

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.7.1~~ fix(deps): update dependency eslint-plugin-import-x to v4.7.2 Mar 16, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from c57f2ba to c0cc8f3 Compare March 16, 2025 14:15

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.7.2~~ fix(deps): update dependency eslint-plugin-import-x to v4.8.0 Mar 16, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from 037188e to e69f4c7 Compare March 18, 2025 19:26

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.8.0~~ fix(deps): update dependency eslint-plugin-import-x to v4.8.1 Mar 18, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from 3346c10 to 3ce7bd0 Compare March 18, 2025 23:09

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.8.1~~ fix(deps): update dependency eslint-plugin-import-x to v4.9.0 Mar 18, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from d3a25dd to 41e85ca Compare March 20, 2025 05:49

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.9.0~~ fix(deps): update dependency eslint-plugin-import-x to v4.9.1 Mar 20, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from c170312 to de24357 Compare March 25, 2025 11:44

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.9.1~~ fix(deps): update dependency eslint-plugin-import-x to v4.9.2 Mar 25, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from 380fefb to 34f6fa3 Compare March 26, 2025 12:28

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.9.2~~ fix(deps): update dependency eslint-plugin-import-x to v4.9.3 Mar 26, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from eb0e36e to c075d5a Compare March 29, 2025 22:34

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.9.3~~ fix(deps): update dependency eslint-plugin-import-x to v4.9.4 Mar 29, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from d39c580 to 3e25da9 Compare April 1, 2025 06:50

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.9.4~~ fix(deps): update dependency eslint-plugin-import-x to v4.10.0 Apr 1, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from 377452d to b29dd2f Compare April 6, 2025 05:17

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.10.0~~ fix(deps): update dependency eslint-plugin-import-x to v4.10.1 Apr 6, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from 0ff73a4 to b5b61b1 Compare April 7, 2025 05:51

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.10.1~~ fix(deps): update dependency eslint-plugin-import-x to v4.10.2 Apr 7, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from 66485f5 to ba1adfa Compare April 13, 2025 10:03

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.10.2~~ fix(deps): update dependency eslint-plugin-import-x to v4.10.3 Apr 13, 2025

renovate Bot force-pushed the renovate/eslint-plugin-import-x-4.x branch from ea6b6b4 to 8c4db1d Compare April 15, 2025 12:59

renovate Bot changed the title ~~fix(deps): update dependency eslint-plugin-import-x to v4.10.3~~ fix(deps): update dependency eslint-plugin-import-x to v4.10.4 Apr 15, 2025

renovate Bot and others added 2 commits July 24, 2026 19:50

fix(deps): update dependency eslint-plugin-import-x to v4.17.1

330de2e

chore(dependencies): updated changesets for modified dependencies

6d2223a

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update dependency eslint-plugin-import-x to v4.17.1 - #425

fix(deps): update dependency eslint-plugin-import-x to v4.17.1#425
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/eslint-plugin-import-x-4.x

renovate Bot commented Aug 26, 2024 •

edited

Loading

Uh oh!

changeset-bot Bot commented Aug 26, 2024 •

edited

Loading

Uh oh!

nx-cloud Bot commented Aug 26, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Aug 26, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

For eslint-plugin-import-x users

For custom import resolver developers

Patch Changes

Configuration

Uh oh!

changeset-bot Bot commented Aug 26, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

nx-cloud Bot commented Aug 26, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

☁️ Nx Cloud Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Aug 26, 2024 •

edited

Loading

For `eslint-plugin-import-x` users

changeset-bot Bot commented Aug 26, 2024 •

edited

Loading

nx-cloud Bot commented Aug 26, 2024 •

edited

Loading