Repository navigation
chore: switch the test runner to vitest - #4
Merged
Merged
Conversation
The /iso entry was upstream's experiment for sharing one TypeScript frontend with a native host (scriptc-game): csrc/flat.cpp with fixed 16384-slot tables and a single-world assumption, src/frontend.ts built with a tsc --ignoreConfig hack, and a v0 surface (world, body, box, sphere) that nothing outside the repo's own test consumed. It also leaked the _b3f_* exports into the generated declarations. The fork's public API is the embind surface (soon a flat C ABI with its own TypeScript frontend), so the layer is dropped: files, the ./iso package export, the build step and the README section. BREAKING CHANGE: the `@frsource/box3d-wasm/iso` entry no longer exists. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Same three test files, same assertions; only the runner import changes. vitest brings the typecheck project (test/**/*.test-d.ts, empty for now) that the upcoming TypeScript frontend uses for its type tests, inline snapshots for event records, and the bench runner, and it matches the toolset of @frsource/babylon-box3d. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was referenced Oct 7, 2026
…loy (#5) Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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.
Stacked on #3 (merge that first; GitHub retargets this one to
mainwhen the base branch is deleted).Why
The binding rewrite tracked for 1.0 needs type tests (
*.test-d.tswithexpectTypeOf/@ts-expect-error), inline snapshots for event records and a bench runner. vitest provides all three and is what@frsource/babylon-box3dalready uses, so contributors switching between the two repos keep one toolset. Changing the runner in its own PR keeps a later failure attributable.What
vitest@5.0.3devDependency (exact pin, repo style).vitest.config.ts: runtime tests fromtest/**, typecheck project enabled fortest/**/*.test-d.ts(no files yet).testfromvitestinstead ofnode:test; assertions unchanged (node:assert/strict).test→vitest run, newtest:dev→vitest.Verification
pnpm test: 3 files, 23 tests passing, type errors none, ~0.8 s; the threaded build does not keep the process alive.pnpm lintclean.🤖 Generated with Claude Code