🐛 fix(ci): Use workspace-level package-lock.json for npm installs #142
Merged
trickpatty merged 1 commit intomainfrom Jan 18, 2026
Merged
🐛 fix(ci): Use workspace-level package-lock.json for npm installs #142trickpatty merged 1 commit intomainfrom
trickpatty merged 1 commit intomainfrom
Conversation
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/)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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: