[Bug]: new catalog feature fails with typescript@catalog

[snebjorn]

Self-service

• I'd be willing to implement a fix

Describe the bug

yarn install fails when using the new catalogs feature

To reproduce

# yarnrc.yml
nodeLinker: node-modules

catalog:
  typescript: 5.9.2

// package.json snippet
"devDependencies": {
    "typescript": "catalog:",
}

$ yarn
➤ YN0000: · Yarn 4.10.2
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: typescript@catalog: isn't supported by any available resolver
    at rm.getResolverByDescriptor (omitted\AppData\Local\node\corepack\v1\yarn\4.10.2\yarn.js:141:1698)
    at rm.bindDescriptor (omitted\AppData\Local\node\corepack\v1\yarn\4.10.2\yarn.js:141:1083)
    at omitted\AppData\Local\node\corepack\v1\yarn\4.10.2\yarn.js:209:8315
    at Array.map (<anonymous>)
    at mt (omitted\AppData\Local\node\corepack\v1\yarn\4.10.2\yarn.js:209:8286)
    at omitted\AppData\Local\node\corepack\v1\yarn\4.10.2\yarn.js:209:8998
    at async Promise.allSettled (index 34)
    at async Uu (omitted\AppData\Local\node\corepack\v1\yarn\4.10.2\yarn.js:140:44361)
➤ YN0000: └ Completed
➤ YN0000: · Failed with errors in 0s 176ms

Environment

System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 AMD Ryzen 7 7800X3D 8-Core Processor
  Binaries:
    Node: 24.8.0 - ~\AppData\Local\Temp\xfs-96c20457\node.CMD
    Yarn: 4.10.2 - ~\AppData\Local\Temp\xfs-96c20457\yarn.CMD
    npm: 11.6.0 - C:\Program Files\nodejs\npm.CMD
    bun: 1.2.22 - ~\.bun\bin\bun.EXE

Additional context

No response

[joshgummersall]

Somehow this seems to reproduce for me, on a Mac, using 4.10.3, only for typescript! It works for other catalog entries (both in default catalog and named catalog).

[RomainLanz]

I can confirm I have the same issue with latest release of Yarn on macOS and only for TypeScript

[connect-kai]

+1