Skip to content

fix(deps): sync bun.lock with package.json - #5

Merged
ChiragAgg5k merged 1 commit into
mainfrom
fix-ci
Nov 3, 2026
Merged

ChiragAgg5k merged 1 commit into
mainfrom
fix-ci

Conversation

@ChiragAgg5k

Copy link
Copy Markdown
Member

Cause

package.json gained and bumped dependencies (appwrite, prismjs, react-syntax-highlighter, @types/prismjs, newer @tanstack/react-start and @tanstack/nitro-v2-vite-plugin ranges, @types/node) without bun.lock being updated. bun install --frozen-lockfile in the verify job in #4 refuses the stale lock.

After the install passes, bun run test (vitest run) also fails: the repository has no test files yet, and vitest exits 1 when it finds none.

Fix

  • Run bun install with Bun 1.4.4 (the version setup-bun installs in CI) to bring bun.lock in line with package.json.
  • Run vitest run --passWithNoTests, so the test script passes while there are no tests and still runs any that are added.
  • Add the shared verify caller (identical to ci: verify builds with the shared workflow #4) so this PR runs the same check.

Verification

With Bun 1.4.4: bun install --frozen-lockfile, bun run build and bun run test all exit 0.

Unblocks #4.

Dependencies were added and bumped in package.json without updating bun.lock, so bun install --frozen-lockfile failed. vitest run also exits 1 with no test files, and the repository has none yet.
@ChiragAgg5k
ChiragAgg5k merged commit fe71dcb into main Nov 3, 2026
2 checks passed
@ChiragAgg5k
ChiragAgg5k deleted the fix-ci branch November 3, 2026 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant