Skip to content

🐛 fix(ci): Use workspace-level package-lock.json for npm installs #142

Merged
trickpatty merged 1 commit intomainfrom
claude/fix-display-build-pipeline-6RFqd
Jan 18, 2026
Merged

🐛 fix(ci): Use workspace-level package-lock.json for npm installs #142
trickpatty merged 1 commit intomainfrom
claude/fix-display-build-pipeline-6RFqd

Conversation

@trickpatty
Copy link
Owner

The clients/ directory has an npm workspaces configuration which requires a single package-lock.json at the workspace root instead of individual lock files in each workspace package.

Changes:

  • Add workspace-level package-lock.json at clients/
  • Remove individual package-lock.json from clients/display/ and clients/web/
  • Update electron.yml, angular.yml, and deploy.yml workflows to:
    • Reference the workspace-root package-lock.json for caching
    • Run npm ci from the workspace root (clients/)

The clients/ directory has an npm workspaces configuration which
requires a single package-lock.json at the workspace root instead
of individual lock files in each workspace package.

Changes:
- Add workspace-level package-lock.json at clients/
- Remove individual package-lock.json from clients/display/ and clients/web/
- Update electron.yml, angular.yml, and deploy.yml workflows to:
  - Reference the workspace-root package-lock.json for caching
  - Run npm ci from the workspace root (clients/)
@trickpatty trickpatty merged commit 91f3a11 into main Jan 18, 2026
16 checks passed
@trickpatty trickpatty deleted the claude/fix-display-build-pipeline-6RFqd branch January 18, 2026 18:56
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.

2 participants