[PM-34668] fix(desktop): sync @napi-rs/cli lockfile entry#19997
Open
caverav wants to merge 3 commits into
Open
[PM-34668] fix(desktop): sync @napi-rs/cli lockfile entry#19997caverav wants to merge 3 commits into
caverav wants to merge 3 commits into
Conversation
Collaborator
|
Thank you for your contribution! We've added this to our internal Community PR board for review. Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process. |
Author
|
Hi, any update on this? It's causing bugs in downstream builds. |
1 task
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.
Summary
Sync the stale
@napi-rs/clientry in the rootpackage-lock.jsonwith the version already declared byapps/desktop/desktop_native/napi/package.json.The desktop NAPI workspace already depends on
@napi-rs/cli3.5.1, but the nested lockfile entry still points to3.2.0.Why
This keeps the workspace and lockfile consistent and avoids downstream/offline tooling failures caused by the mismatch.
Notes
There is already an open draft PR touching this as part of a larger Angular/Storybook update, but this change is standalone and limited to the lockfile inconsistency.