Verify latest release
pnpm version
10.29.2
Which area(s) of pnpm are affected? (leave empty if unsure)
Dependencies resolver
Link to the code that reproduces this issue or a replay of the bug
No response
Reproduction steps
Have a catalog for entry for a dependency, that also has an executable in the pnpm-workspace (e.g. turbo), then use dlx with the version pointing at the catalog entry (e.g. pnpm dlx turbo@catalog:).
Describe the Bug
We seem to be getting a ERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC, while pnpm config list does show the dependency listed. Perhaps the catalogs are not fetched from the workspace file when using dlx?
I thought it did, as some other stuff is read from the workspace file
Related #10434 & #10249
Expected Behavior
Use version specified in pnpm-workspace
Which Node.js version are you using?
24.13.0
Which operating systems have you used?
If your OS is a Linux based, which one it is? (Include the version if relevant)
No response
Verify latest release
pnpm version
10.29.2
Which area(s) of pnpm are affected? (leave empty if unsure)
Dependencies resolver
Link to the code that reproduces this issue or a replay of the bug
No response
Reproduction steps
Have a catalog for entry for a dependency, that also has an executable in the pnpm-workspace (e.g.
turbo), then use dlx with the version pointing at the catalog entry (e.g.pnpm dlx turbo@catalog:).Describe the Bug
We seem to be getting a
ERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC, whilepnpm config listdoes show the dependency listed. Perhaps the catalogs are not fetched from the workspace file when using dlx?I thought it did, as some other stuff is read from the workspace file
Related #10434 & #10249
Expected Behavior
Use version specified in pnpm-workspace
Which Node.js version are you using?
24.13.0
Which operating systems have you used?
If your OS is a Linux based, which one it is? (Include the version if relevant)
No response