✅ Deploy Preview for viteplus-preview canceled.

Why it fails under yarn's nodeLinker: pnpm but not under pnpm

Core does a runtime import.meta.resolve('@typescript/native-preview') (a phantom dep it never declares). Both pnpm and yarn's pnpm linker use a store + symlinks, so why does this resolve under pnpm but break under yarn? One directory: pnpm has a global hoist dir inside the store; yarn's pnpm linker doesn't.

pnpm

node_modules/
  .pnpm/
    @voidzero-dev+vite-plus-core@x.y.z/
      node_modules/
        @voidzero-dev/vite-plus-core/   <- real files
        <core's declared deps>          -> symlinks
    @typescript+native-preview@a.b.c/
      node_modules/@typescript/native-preview/
    node_modules/                        <- catch-all hoist (hoist-pattern=['*'])
      @typescript/native-preview         -> symlink
      ...~every package in the graph...
  <project's direct deps>                -> symlinks into .pnpm

Resolving native-preview from core walks up to .pnpm/node_modules/ and finds it. pnpm is strict only at the project root; deeper in the store, any dep can reach almost any package (a deliberate compat compromise).

yarn nodeLinker: pnpm

node_modules/
  .store/
    @voidzero-dev-vite-plus-core-virtual-f02751107a/
      node_modules/
        @voidzero-dev/vite-plus-core/   <- real files
        <core's declared deps>          -> symlinks
    (no global .store/node_modules catch-all)
  <project's direct deps>               -> symlinks into .store

Same shape, but no catch-all. Each package sees only its declared (+ injected peer) deps, so the walk-up finds nothing and resolution fails.

Takeaway: yarn's nodeLinker: pnpm is actually stricter than pnpm, so it breaks phantom deps that real pnpm quietly hides, here vp pack. node-modules hid the problem via full hoisting.

Fix: declare @typescript/native-preview in @voidzero-dev/vite-plus-core (likely an optionalDependency); that's correct under every layout (yarn pnpm linker, PnP, pnpm). packageExtensions is a yarn-only band-aid.