Skip to content

docs: Windows npm ci EPERM troubleshooting #166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tass500 merged 1 commit into from
Apr 13, 2026
Merged

docs: Windows npm ci EPERM troubleshooting #166

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ Thanks for your interest in contributing.

- Install:
- `cd frontend && npm ci`
- **Windows — `EPERM` / `unlink` during `npm ci` (often `esbuild.exe`):** stop the dev server first (**Ctrl+C** where `npm start` / `ng serve` is running). Those processes lock files under `node_modules`. If it persists, end stray **Node.js** processes in Task Manager or add a short-lived antivirus exclusion for the repo folder.
- Dev server — `frontend/proxy.conf.json` proxies **`/api`** → **`http://localhost:5002`** with **`changeOrigin: false`** (keep backend `Host` aligned with the SPA origin for tenant + BFF):
- `npm start` or `ng serve` (default **http://localhost:4200**)
- Lint:
Expand Down
7 changes: 4 additions & 3 deletions frontend/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,10 @@ Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.

Tests live in `e2e/`. The **CI smoke** suite is `e2e/smoke.spec.ts` only.

1. Install Chromium (once per machine): `npm run e2e:install-browsers`
2. **Recommended (repo root):** start backend + dev server via `bash scripts/e2e-smoke-ci.sh` (Unix) or `powershell -File scripts/e2e-smoke-ci.ps1` (Windows), which set `PW_NO_WEBSERVER=1` and run `npm run e2e:smoke` in this directory.
3. **Manual:** run the backend on **:5002** and `npm start` here on **:4200**, then in this directory:
1. Install dependencies: `npm ci` (if **`EPERM`** on Windows, stop **`npm start`** / **`ng serve`** first — see [`CONTRIBUTING.md`](../../CONTRIBUTING.md)).
2. Install Chromium (once per machine): `npm run e2e:install-browsers`
3. **Recommended (repo root):** start backend + dev server via `bash scripts/e2e-smoke-ci.sh` (Unix) or `powershell -File scripts/e2e-smoke-ci.ps1` (Windows), which set `PW_NO_WEBSERVER=1` and run `npm run e2e:smoke` in this directory.
4. **Manual:** run the backend on **:5002** and `npm start` here on **:4200**, then in this directory:
- **Unix:** `PW_NO_WEBSERVER=1 npm run e2e:smoke`
- **Windows (cmd):** `set PW_NO_WEBSERVER=1&& npm run e2e:smoke`

Expand Down
Loading