Fix/ci tsconfig stylekit core styles - #25
Conversation
…resolve it packages/mcp/src/data.ts imports from "stylekit-core/styles", but the root tsconfig paths only mapped "stylekit-core" and "stylekit-core/discovery". CI runs `tsc --noEmit` and `next build` without pre-building the core package, so the unmapped subpath could not be resolved from source and both jobs failed with TS2307 "Cannot find module 'stylekit-core/styles'". Add the missing path entry, mirroring the existing discovery mapping. Verified: `tsc --noEmit` passes even with packages/core/dist removed, proving resolution now comes from source as CI needs.
check:product-truth failed with toolkit-repository-version-mismatch because the Developer Toolkit manifest's repositoryVersion lagged the package.json bumps. repositoryVersion documents the in-repo version and must mirror package.json, so align cli 0.1.1->0.1.2, core 1.0.0-beta.1->1.0.0-beta.3, and mcp 0.1.1->0.2.0. publicVersion and the install commands (the npm-published claims) are deliberately left unchanged. Update the developer-toolkit test's hardcoded cli repositoryVersion to match, resolving its contradiction with the product-truth invariant.
|
Someone is attempting to deploy a commit to the Anx's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
Next review available in: 35 minutes Limit details: You’ve used all 2 included reviews currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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 |
1 participant
Summary
What changed:
Why:
Change Type
feat— new feature or stylefix— bug fixrefactor— code improvement (no behavior change)docs— documentation onlychore— build, CI, or toolingScope
Style Contribution Checklist
___docs/STYLE_ADDITION_CHECKLIST.mdcompletely/styles/<slug>loads correctly/styles/<slug>/showcaserenders all 12+ sectionsValidation
pnpm run security:secrets— no secrets detectedpnpm run lint— no errorsnpx tsc --noEmit— no type errorspnpm test— all tests passpnpm build— builds successfullySecurity
.envfiles committedNEXT_PUBLIC_Breaking Changes
Screenshots
Notes for Reviewers