Skip to content

Fix Windows frontend preparation with isolated installs - #80

Merged
dovvnloading merged 1 commit into
mainfrom
codex/isolated-frontend-preparation
Jul 30, 2026
Merged

Fix Windows frontend preparation with isolated installs#80
dovvnloading merged 1 commit into
mainfrom
codex/isolated-frontend-preparation

Conversation

@dovvnloading

Copy link
Copy Markdown
Owner

Problem

pm ci modified the live frontend/node_modules directory. When a running Vite process held Rolldown's native Windows binding, npm failed with EPERM and left the install partially removed.

Fix

  • stage frontend build inputs beside the source tree
  • run npm ci and the production build only in the isolated staging tree
  • atomically publish the generated dist bundle
  • clean staging on success and failure
  • add regression coverage for live-install preservation

Verification

  • python -m ruff check backend tests tools main.py`n- python -m pytest -q (374 passed, 1 skipped)
  • reproduced python main.py --build-frontend while Vite held the native binding; build passed

@dovvnloading
dovvnloading merged commit 39ec89b into main Jul 30, 2026
1 check passed
@dovvnloading
dovvnloading deleted the codex/isolated-frontend-preparation branch July 30, 2026 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant