chore: upgrade app platform dependencies#597
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
mainand the later MCP/auth dependency updates frommainwhile keeping this PR scoped to React Router, Vite, TypeScript, Tailwind, Vitest, Playwright, and esbuildbaseUrlsetting frompackages/workshop-app/tsconfig.jsonso the TypeScript 6 upgrade typechecks cleanlymainsync so they reflect the latest tooling/auth baseline plus the app platform upgradeTest Plan
npm installnpm run validatenpm run testmainafter the NX/workspace tooling PR and rerunnpm run validatenpm run testafter the NX/workspace tooling mergemainagain after the MCP/auth dependency PR and rerunnpm run validatenpm run testafter the MCP/auth mergeNotes
mainthrough merge commit7eab68e8, after absorbing both84173232(NX/workspace tooling) ande882eead(MCP/auth dependency group)npm run testtransiently failed inpackages/workshop-mcp/src/mcp-client.test.ts; the isolated MCP test file passed immediately after, and a fullnpm run testrerun also passed without code changes, so I did not widen scope into that upstream areanpm run validatestill reports existing warning-level lint findings inpackages/workshop-mcp/src/utils.test.ts, but validation succeeds and this PR does not expand into that separate cleanupArtifacts