Commit 246d006
committed
ci: opt the consumer test into running node-libcurl's install scripts
pnpm v10 no longer runs dependency install scripts by default — every
package that needs preinstall/install/postinstall now has to be on the
consumer's allow-list. The windows-consumer-install workflow saw the
exact symptom: `pnpm add` reported "Ignored build scripts: node-libcurl"
and the install "succeeded", but vcpkg never ran, so the curl.exe sanity
check threw "vcpkg curl.exe was not found after install".
Opt in two ways so both invocations and any followup script behave the
same: the consumer package.json now declares
`pnpm.onlyBuiltDependencies = ["node-libcurl"]`, and the `pnpm add`
command also passes `--allow-build node-libcurl` (belt-and-braces for
the one-shot install).
This is the same hoop a real pnpm-v10 user has to jump through — so
keeping the workaround in the workflow rather than hiding it behind a
custom action means the CI continues to reflect what consumers
actually experience.1 parent 785f589 commit 246d006
1 file changed
Lines changed: 18 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
64 | 64 | | |
65 | 65 | | |
66 | 66 | | |
67 | | - | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
68 | 84 | | |
69 | | - | |
| 85 | + | |
70 | 86 | | |
71 | 87 | | |
72 | 88 | | |
| |||
0 commit comments