Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f3e25a7045
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "postcss": "^8.5.8", | ||
| "tailwindcss": "4.2.2", | ||
| "typescript": "5.9.3", | ||
| "typescript": "6.0.2", |
There was a problem hiding this comment.
Keep TypeScript within parser's supported range
This commit pins typescript to 6.0.2, but the same template lockfile still resolves @typescript-eslint/parser@8.57.2 with a peer constraint of typescript >=4.8.4 <6.0.0 (templates/plate-template/bun.lock:383, and similarly in templates/plate-playground-template/bun.lock:675). That creates an unsupported eslint/type parser toolchain for generated apps, which can fail in environments that enforce peer deps and can produce unstable lint/type-aware behavior; either keep TypeScript on 5.x or upgrade the eslint parser stack to a version that explicitly supports TS 6 in both templates.
Useful? React with 👍 / 👎.
Template sync after release produced changes but did not pass automation.
pnpm templates:update --local:successfailure