chore(experiment): drop windows --linker=hoisted to test if alignment alone fixes CI

If dep alignment alone eliminates the workspace-scoped nested installs that
bun's Windows isolated layout can't materialize, then this PR's workflow
change is dead weight. Reverting it to see if Windows CI still greens with
isolated linker + aligned deps + source-level v25 fixes.
This commit is contained in:
James
2026-05-13 03:48:52 +00:00
parent 067bc722e3
commit 5affe1322a
+2 -20
View File
@@ -150,16 +150,7 @@ jobs:
- name: Install dependencies
shell: pwsh
# Force the pre-1.3 "hoisted" linker on Windows. Bun 1.3.x's default
# "isolated" linker creates nested workspace junctions that don't
# materialize reliably on Windows GHA runners — manifests as
# `Cannot find package 'esbuild'` walking up from
# `packages/producer/build.mjs` and `EPERM stat` on
# `packages/producer/node_modules/@fontsource/*` from generators.
# See oven-sh/bun#23615, #18354, #10146. Linux CI keeps isolated;
# the lockfile is linker-agnostic so this flag is safe with
# --frozen-lockfile.
run: bun install --frozen-lockfile --linker=hoisted
run: bun install --frozen-lockfile
- name: Build all packages
shell: pwsh
@@ -380,16 +371,7 @@ jobs:
- name: Install dependencies
shell: pwsh
# Force the pre-1.3 "hoisted" linker on Windows. Bun 1.3.x's default
# "isolated" linker creates nested workspace junctions that don't
# materialize reliably on Windows GHA runners — manifests as
# `Cannot find package 'esbuild'` walking up from
# `packages/producer/build.mjs` and `EPERM stat` on
# `packages/producer/node_modules/@fontsource/*` from generators.
# See oven-sh/bun#23615, #18354, #10146. Linux CI keeps isolated;
# the lockfile is linker-agnostic so this flag is safe with
# --frozen-lockfile.
run: bun install --frozen-lockfile --linker=hoisted
run: bun install --frozen-lockfile
- name: Build
shell: pwsh