fix: restore cross-platform optional deps in root lockfile#136
Merged
Conversation
Regenerating the lock with rm + npm install on macOS stripped the linux-x64 rolldown/vitest native bindings (npm optional-deps bug npm/cli#4828), so the SDK publish workflow's npm test failed on CI with 'Cannot find native binding'. Restored the multi-platform lock and re-synced lightnode-sdk to 0.19.2 in place.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 sdk-v0.19.2 publish failed at the CI test step with 'Cannot find native binding' for @rolldown/binding-linux-x64-gnu. Cause: regenerating the lock via rm + npm install on macOS recorded only the darwin bindings (npm optional-deps bug npm/cli#4828). Restored the multi-platform lock (12 linux binding refs) and re-synced lightnode-sdk 0.19.2 in place.