Environment

Installing nuxt-nightly@5x aliased to the nuxt name fails to install properly in pnpm, resulting in a permanent hang due to a cyclical peer dependency.

Reproduction

mkdir nuxt-pnpm-hang
cd nuxt-pnpm-hang
echo {} > package.json
pnpm i nuxt@npm:nuxt-nightly@5x

Describe the bug

Resulting output:

$ pnpm i nuxt@npm:nuxt-nightly@5x
Progress: resolved 416, reused 328, downloaded 0, added 0

Additional context

1. nuxt-nightly@5.0.0-... depends on "@nuxt/nitro-server": "npm:@nuxt/nitro-server-nightly@<exact same version>".
2. @nuxt/nitro-server-nightly declares "peerDependencies": { "nuxt": "npm:nuxt-nightly@<exact same version>" }. This is a self-referencing aliased peer dep that loops back to the top-level dependency being installed.
3. pnpm's peer-dependency resolver deadlocks on this cycle: process goes to 0% CPU, no open sockets, threads parked in kevent/uv_cond_wait. Resolution shows resolved 416, reused 328 , then hangs forever.

This is possibly a pnpm error, as npm and yarn can install with the alias.