fb4bd0b777`actions/setup-node@v6.4.0` with `cache: 'npm'` silently aborts the entire job on Windows runners when the npm cache path returned by `npm config get cache` (`C:\npm\cache`) does not yet exist on a fresh runner -- the step exits 24s in with no error message and every following step gets skipped. See npm/cli#7308 for the underlying EEXIST / missing-dir race in the npm cache directory. This mirrors the existing precedent in `studio-windows-ui-smoke.yml`'s `setup-python` block, which already dropped `cache: 'pip'` for the same reason (post-step fatal error on a missing pip cache dir). The frontend `npm ci` is fast enough without the cache that the reliability gain is worth the ~30s. |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| dependabot.yml | ||
| FUNDING.yml | ||