Repository navigation
Migrate to TypeScript and Oxc; improve Food Guide usability - #87
Merged
Merged
Conversation
Add non-color selection cues and preserve readable forced-color states. Show localized recovery messages for failed ingredient actions and clean up temporary feedback without animation listeners. Exclude summary rows when finding the highest cooking priority, with regressions for Meatballs and negative recipe priorities.
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
Migrate the Food Guide's data, calculation logic, browser UI, and asset tooling to strict TypeScript, replace ESLint/Prettier with oxlint/oxfmt, and require Node.js 24 or newer. This also incorporates the usability, accessibility, analyzer, navigation, and personal-data improvements developed throughout the migration.
TypeScript, tooling, and maintainability
src/and sprite tooling intotools/. Compile JavaScript and declarations into the existinghtml/paths; generated output stays out of Git. Development, tests, deployment, and packaging build those files automatically.Ingredient picking and cooking views
Browse the complete statistics dataset
Navigation and personal data
Accessibility and interface polish
Compatibility and rollout
Source checkouts and deployments now require a build and Node 24+. Public module URLs and library entrypoints remain compatible, and legacy saved preferences/ingredient IDs are restored. Personal data stays in the browser's local profile; a share snapshot or JSON export is an explicit user action. Analyzer pagination bounds the rendered table; combination calculation remains combinatorial and retains its results in browser memory, with pause and refresh available during long runs.
The companion desktop PR #33 bundles this guide revision. Merge the guide first. If this PR is squash-merged or rebased, update the desktop submodule pin to the resulting commit on
mainbefore merging the desktop PR; a merge commit preserves the existing pin.Validation