Repository navigation
Conversation
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.
Problem
At c24004d, package.json declares optional dependencies on @esbuild/linux-x64 and @rollup/rollup-linux-x64-gnu, but the root workspace in bun.lock does not. A frozen install fails with:
Change
Regenerate bun.lock with Bun 1.4.5 to record both optional dependencies. The existing transitive esbuild 0.25.5 and Rollup 4.43.0 binaries remain separately locked; the direct optional dependencies resolve within their declared ranges. No manifest or application-code changes.
Verification
On Windows x64 using Bun 1.4.5, fresh isolated fixtures contained the same upstream package.json and either the original or repaired lockfile. Each ran:
Scope and limitations
This verifies frozen dependency installation on Windows, not Linux native-binary execution. Lifecycle scripts were disabled in the isolated check. The desktop build and manual GUI test could not complete because the local managed endpoint blocked generated Rust build-script execution; this PR does not claim to fix that separate environment restriction.