Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug?]: Error: Qualified path resolution failed: we looked for the following paths, but none could be accessed. #6577

Open
1 task
demonicattack opened this issue Oct 25, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@demonicattack
Copy link

demonicattack commented Oct 25, 2024

Self-service

  • I'd be willing to implement a fix

Describe the bug

I encountered an error related to qualified path resolution while using Yarn Berry. The error message indicates that a specific source path could not be accessed.

To reproduce

I am trying to generate types for ESLint using tsx, but I am encountering an error related to qualified path resolution.

use Nodejs 22.9.0

"typegen": "tsx src/scripts/typegen.ts"

Image

"typegen": "yarn dlx @yarnpkg/pnpify run tsx src/scripts/typegen.ts"

Image

use Nodejs 23.0.0

"typegen": "tsx src/scripts/typegen.ts"

same error

"typegen": "yarn dlx @yarnpkg/pnpify run tsx src/scripts/typegen.ts"

Image

Reproduction Steps:

  • Attempt to generate types for ESLint using tsx.
  • Observe the error message indicating that the specified path could not be found.
  • Repeat the same steps using ts-node instead of tsx.
  • Observe that the same error occurs.
  • Expected Behavior: The types should be generated correctly without any path resolution errors.

Repository:

My repository: my repo

Similar Issues:

tsx: tsx issue

Environment

Ubuntu 24.04
Node.js version: 22.9.0 && 23.0.0
Yarn version: 4.5.1
TypeScript version: 5.6.3
Yarn workspaces

Maybe it's worth adding tsx support to the @yarnpkg/sdks

@demonicattack demonicattack added the bug Something isn't working label Oct 25, 2024
@demonicattack
Copy link
Author

To date, I have only been able to resolve this issue by using nodeLinker: node-modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant