Fix: remove bun lockfile for dependency updates (#79)#223
Open
leventyayla wants to merge 1 commit into
Open
Conversation
…ircuit#79) - Remove bun.lock from repository (lockfile saving disabled in bunfig.toml) - Add bun.lock and bun.lockb to .gitignore - This prevents Vercel OOM errors during dependency resolution (issue tscircuit#78)
|
Someone is attempting to deploy a commit to the tscircuit Team on Vercel. A member of the Team first needs to authorize it. |
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
/claim #79
This PR addresses the Vercel deployment OOM issue described in #78/#79.
Changes
bun.lockfrom the repository — lockfile saving is already disabled inbunfig.tomlvia[install.lockfile] save = falsebun.lockandbun.lockbto.gitignoreto prevent future accidental commitsWhy this matters
The lockfile causes Vercel to run out of memory during dependency resolution on their smaller build instances. Removing it from the repo forces fresh resolution on each deploy without the memory-heavy lockfile diff overhead.
Notes
bunfig.tomlwas already configured correctly — this PR just removes the committed lockfile and prevents it from coming backVerification
bun installsucceeds with no lockfile generated[install.lockfile] save = falseinbunfig.tomlprevents future lockfile creationCloses #79
Verification note: Vercel deployment could not be verified from this PR because the Vercel check requires project authorization; no application secret or token was used or exposed.