Path resolution error when starting @eslint/config-inspector in projects using Yarn's Plug 'N Play feature.

[robmisasi]

Description

When running instructions starting the inspector (yarn dlx @eslint/config-inspector), the following error is produced and the inspector fails to start:

node:internal/modules/run_main:107
    triggerUncaughtException(
    ^
Error: Qualified path resolution failed: we looked for the following paths, but none could be accessed.

Source path: C:\Users\RMisasi\AppData\Local\Temp\xfs-0741eebd\dlx-51652\.yarn\__virtual__\@eslint-config-inspector-virtual-7b0fac6ca2\0\cache\@eslint-config-inspector-npm-1.4.1-a30f94c4a4-daa23a88f2.zip\node_modules\@eslint\config-inspector\dist\cli.js
Not found: C:\Users\RMisasi\AppData\Local\Temp\xfs-0741eebd\dlx-51652\.yarn\__virtual__\@eslint-config-inspector-virtual-7b0fac6ca2\0\cache\@eslint-config-inspector-npm-1.4.1-a30f94c4a4-daa23a88f2.zip\node_modules\@eslint\config-inspector\dist\cli.js

    at makeError (C:\Users\RMisasi\AppData\Local\Temp\xfs-0741eebd\dlx-51652\.pnp.cjs:6263:34)
    at resolveUnqualified (C:\Users\RMisasi\AppData\Local\Temp\xfs-0741eebd\dlx-51652\.pnp.cjs:8003:13)
    at resolveRequest (C:\Users\RMisasi\AppData\Local\Temp\xfs-0741eebd\dlx-51652\.pnp.cjs:8043:14)
    at Object.resolveRequest (C:\Users\RMisasi\AppData\Local\Temp\xfs-0741eebd\dlx-51652\.pnp.cjs:8099:26)
    at resolve$1 (file:///C:/Users/RMisasi/AppData/Local/Temp/xfs-0741eebd/dlx-51652/.pnp.loader.mjs:2043:21)
    at nextResolve (node:internal/modules/esm/hooks:785:28)
    at AsyncLoaderHooksOnLoaderHookWorker.resolve (node:internal/modules/esm/hooks:271:30)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:251:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:845:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)

Node.js v24.11.1

Steps to reproduce

I've created a repository reproducing the issue here:

1. Clone the above repository.
2. Install dependencies with yarn install
3. Run yarn dlx @eslint/config-inspector

Expected behavior

yarn dlx @eslint/config-inspector successfully starts the inspector.

Actual behavior

The inspector fails to start and the error mentioned above is produced.

Workarounds

Prior to v1.4.1, it was possible to install @eslint/config-inspector locally and use yarn run config-inspector to successfully start the inspector in projects using Yarn's Plug 'N Play feature. This is not possible in v1.4.1.

Interestingly it was possible to successfully start the inspector in Plug 'N Play projects via yarn run eslint --inspect-config when v1.3.0 was the latest version of the inspector, but since this instruction fetches the latest version of @eslint/config-inspector, this is no longer possible.

System Details

Operating System: Windows 11
Package Manager: yarn@4.11.0
Node: 24.11.1

Other Notes

While yarn dlx @eslint/config-inspector is not a documented startup command, npx cannot resolve modules installed by yarn. yarn dlx is the documented alternative to npx in the Yarn ecosystem, and instructions utilizing npx are expected to behave the same way when yarn dlx is substituted.

[github-actions]

Oops! It looks like we lost track of this issue. What do we want to do here? This issue will auto-close in 7 days without an update.