chore: drop vite-plugin-checker and tidy vite config types#12304
chore: drop vite-plugin-checker and tidy vite config types#12304kaladinlight merged 1 commit intodevelopfrom
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR removes the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- remove vite-plugin-checker (CI/editor LSP cover TS errors; was the main local dev perf bottleneck) - type publicFilesEnvVars as Record<string, string> for dynamic VITE_SRI_*/VITE_CID_* keys - suppress multiformats imports whose package.json exports omit type entries Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
9498abc to
678fd8c
Compare
Description
vite-plugin-checkerfrom the dev pipeline (and dependency). It was the dominant local dev perf bottleneck; CI and editor LSP already surface TypeScript errors.publicFilesEnvVarsasRecord<string, string>so the dynamicVITE_SRI_*/VITE_CID_*keys built from thepublic/directory type-check.multiformats/cid|codecs/raw|hashes/sha2imports with@ts-expect-error. multiformats v9 ships types but excludes them from its packageexports, so TS can't resolve them. The package is only used at build time for SRI/CID computation, so suppressing inline is cleaner than declaring ambient modules.Issue (if applicable)
closes #
Risk
Build/dev tooling only; no runtime app code changes. Dev type errors will no longer block via overlay — they still surface in editor and CI.
None.
Testing
Engineering
pnpm installthenpnpm dev— confirm dev server starts and is noticeably faster on cold/warm bootpnpm build— confirm production build still succeeds and emits SRI/CID env vars correctlypnpm type-check— confirm no new TS errorsOperations
Screenshots (if applicable)
🤖 Generated with Claude Code
Summary by CodeRabbit