chore: migrate from pnpm to Bun, bump @vttforge/* to latest - #14
Merged
Merged
Conversation
Switches the package manager and test runner to Bun 1.4.2, matching the SDK itself. package.json's packageManager, both CI workflows (pnpm/action-setup + setup-node -> oven-sh/setup-bun) and the docs now point at bun. pnpm-lock.yaml is gone; bun.lock replaces it. pnpm-workspace.yaml is gone too: its only content was a minimumReleaseAgeExclude allowlist for an age-gate that had no active threshold configured anywhere in this repo or the machine, so there was nothing live to port. vitest -> bun:test in all four test files. Two of them use game.settings.get(...) inside expect().toBe(...); bun:test's matchers bind generically to the subject's inferred type, which Vitest's did not, so those four call sites needed a narrowing cast. Test count is unchanged: 40 tests, 4 files, before and after. @vttforge/core, cli, testing, types and vite-plugin bump to their latest published versions (types jumps three minors: 0.8.0 -> 0.11.1). Typecheck, test, lint and a real release-zip build all pass clean against the bumped set, including the manifest-at-zip-root check.
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
1 participant
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
packageManagerfield, both CI workflows (pnpm/action-setup+setup-node→oven-sh/setup-bun), docs, and lockfile (pnpm-lock.yaml→bun.lock).pnpm-workspace.yamlis dropped. Its only content was aminimumReleaseAgeExcludeallowlist, but the actualminimumReleaseAgethreshold wasn't set anywhere in this repo or the machine's pnpm config, so there was nothing live to carry over.bun:testin all four test files. Test count unchanged: 40 tests, 4 files, before and after.@vttforge/core,cli,testing,typesandvite-pluginbump to their latest published versions (typesjumps three minors: 0.8.0 → 0.11.1).Test plan
bun run typecheck— cleanbun test— 40 pass, 0 fail (matches pre-migration baseline)bun run lint— cleanbun run build(with the CI's manifest/download URL env vars) — real release zip built, manifest confirmed at zip root