build: migrate client and backend to pnpm workspace - #1214
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (26)
💤 Files with no reviewable changes (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe repository now uses a root pnpm workspace for client, server, and shared packages. CI workflows, development guidance, package manifests, and Dockerfiles use pnpm. Node.js 24 configuration and workspace-aware client and server container builds were added. Changespnpm workspace migration
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~30 minutes Change: Other 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 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 |
This branch had an error being deployed
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
1 participant
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.
Client, backend, and shared code currently use separate npm installs and lockfiles. This moves them into one pnpm workspace with shared dependency resolution and root commands for development, builds, tests, and typechecking.
The docs app and React Native SDK remain independent. Docs only gains explicit Next.js roots so the new parent workspace does not change its build boundaries.
Changes
workspace:*for shared code, and replace the three npm lockfiles. Preserve existing resolved package versions and declare dependencies previously accessed through npm hoisting.pino-prettyin backend runtime dependencies, preserve the image's existingNODE_ENVdefault, and exclude local environment files from Docker contexts. Docker builds require BuildKit.Validation
Client lint still fails because of the pre-existing commented-out ESLint configuration. Database migrations were not run during validation.
Summary by CodeRabbit
Documentation
Maintenance