Repository navigation
Address Nuxt audit findings and add regression coverage - #88
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.
Summary
Address the Nuxt audit while retaining static generation and the existing app structure.
Validation
pnpm typecheckpnpm test— 5 passingpnpm buildpnpm test:e2e --project=server— 12 passingpnpm generatepnpm test:output— 4 passingpnpm test:e2e --project=static— 9 passingPerformance
Three post-change cold-cache mobile lab runs: home/experiments total transfer is roughly 75% lower; image transfer is 92–94% lower. Compiled JavaScript remains about 109 kB gzip, below the historical 116 kB review budget. Timing comparisons against the single pre-change run are directional, not field Core Web Vitals.
Audio/MIDI tests use mocked devices; physical hardware was not tested. Previously published drafts remain public until deployment, and this change does not erase prior history.