Repository navigation
refactor: move repository tooling into Rust - #333
Merged
Merged
Conversation
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
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.
Allthing now owns its repository tooling in Rust. Native
xtaskcommands replace Node and shell implementations of build orchestration, Brotli compression, repository/CSP validation, asset-credit auditing, deployment waiting, npm audit handling, browser fixture phases and attestation-key tooling. The isolated SpacetimeDB checks also use Rust; deployment entry points remain thin wrappers.Keep the official Playwright tests, independent crypto/SQL/SDK oracles and required SpacetimeDB TypeScript adapter. The Rust-first policy records the following exceptions: retain the faster JavaScript first-card renderer after its Rust prototype added about 1.1 seconds on the slow-phone profile, and retain the existing small Node static test server after the proposed replacement encountered an unproven pre-mount stall in CI. The failed first run remains rejected. Static startup failures now attach bounded, sanitized transport diagnostics; assertions and timing limits are unchanged.
Validation: