Skip to content

Chore/upgrade toolchain - #91

Merged
veillette merged 5 commits into
mainfrom
chore/upgrade-toolchain
Jun 10, 2026
Merged

Chore/upgrade toolchain#91
veillette merged 5 commits into
mainfrom
chore/upgrade-toolchain

Conversation

@veillette

Copy link
Copy Markdown
Collaborator

No description provided.

veillette and others added 5 commits June 9, 2026 14:40
Bump declared dev-tooling specs to the SceneryStack standard (the repo
already resolved to these via its caret ranges):

- @biomejs/biome ^2.4.2 -> ^2.4.16 (and biome.json $schema -> 2.4.16)
- typescript ~6.0.2 -> ^6.0.3
- vite ^8.0.0 -> ^8.0.16
- engines.node >=20 -> >=22

biome lint (clean), tsc, and vite build pass.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The lockfile was missing the nested @emnapi/core, @emnapi/runtime, and
@emnapi/wasi-threads entries required by the optional
@rolldown/binding-wasm32-wasi binding (Vite 8 / Rolldown), causing
`npm ci` to fail with EUSAGE in CI. Regenerated via `npm install`.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Resolving optional @emnapi/* deps under Node 24 (the version used to
generate package-lock.json, already used by RadioWaves) fixes the
`npm ci` EUSAGE failures seen under Node 22.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
CI (Node 24) ships npm 11.13.0, which resolves the optional
@napi-rs/wasm-runtime peer dep @emnapi/core/@emnapi/runtime to 1.11.0.
A lockfile generated with an older npm omits these entries, so `npm ci`
fails with EUSAGE. Regenerated with the matching npm version.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@veillette
veillette merged commit 42d51ea into main Jun 10, 2026
2 checks passed
@veillette
veillette deleted the chore/upgrade-toolchain branch June 10, 2026 13:39
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