Move to bun and .mise.toml, matching the other -web repos - #4
Merged
Conversation
This was the one static site in the organisation on pnpm, with no .mise.toml at all, while gdam-web, gdlint-web, termcade-web and aviorstudio-web are all bun with the version pinned in mise. pnpm-lock.yaml is replaced by bun.lock, .mise.toml pins bun 1.3, and CI installs the toolchain through mise-action rather than pinning node and pnpm versions in the workflow. That removes three version declarations from YAML -- pnpm 9, node 22, and the implicit lockfile version -- and leaves one, in the file everyone working on this repo already reads. Deliberately its own change rather than folded into the pull request that added CI: a lockfile conversion and a first-ever CI run failing together would have been ambiguous. CI passed on pnpm first; this changes one thing. Verified locally: clean install and build from an empty node_modules, 33 files out, dist/index.html written, same 13 .js as pnpm produced. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
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
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.
This was the one static site in the org on pnpm, with no
.mise.tomlat all, whilegdam-web,gdlint-web,termcade-webandaviorstudio-webare all bun with the version pinned in mise.pnpm-lock.yaml→bun.lock.mise.tomlpinningbun = "1.3"jdx/mise-actionrather thanpnpm/action-setup+actions/setup-nodeThat removes three version declarations from YAML — pnpm 9, node 22, and the implicit lockfile version — and leaves one, in the file everyone working on this repo already reads.
Why this is a separate PR
The PR that added CI here installed from the existing pnpm lockfile deliberately. A lockfile conversion and a first-ever CI run failing together would have been ambiguous about which caused it. CI passed on pnpm first; this changes one thing.
Verified locally
Clean install and build from an empty
node_modules: 33 files out,dist/index.htmlwritten, same 13.jsfiles pnpm produced — so the output is unchanged, only the tooling.