lukevella / rallly

Rallly is an open-source scheduling and collaboration tool designed to make organizing events and meetings easier.
https://rallly.co
GNU Affero General Public License v3.0
3.68k stars 350 forks source link

♻️ Migrate to pnpm #1398

Closed lukevella closed 1 month ago

lukevella commented 1 month ago

Summary by CodeRabbit

Release Notes

vercel[bot] commented 1 month ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 17, 2024 7:32pm
landing ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 17, 2024 7:32pm
coderabbitai[bot] commented 1 month ago

Walkthrough

This pull request modifies the package.json file for the "rallly" project, transitioning several scripts to utilize pnpm instead of prisma and yarn. New scripts have been added, and existing commands have been simplified. The workspaces section has been removed, and dependencies have been updated, including the addition of @radix-ui/react-select and preview-email. The package manager has also been changed from yarn to pnpm. Additionally, the next.config.js file has been updated to enhance Webpack configuration and include a new plugin.

Changes

File Path Change Summary
package.json Updated scripts to use pnpm; added new scripts; removed @prisma/client dependency; added @radix-ui/react-select and preview-email; updated various dependency versions.
apps/web/next.config.js Added @rallly/emails to transpilePackages; updated Webpack function to include isServer; conditionally added PrismaPlugin.

Possibly related PRs

Poem

🐇 In the fields where rabbits play,
PNPM has come to stay!
With actions new and scripts so bright,
Dependencies dance in the morning light.
Hopping along in a workspace cheer,
Our code is tidy, the path is clear! 🌼


📜 Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
📥 Commits Files that changed from the base of the PR and between 15a3ae563f10f9f8aeac1e255f28f37190e084f9 and 48bb8d5326d20d3c097d8e5025844625fbdffcdb.
⛔ Files ignored due to path filters (1) * `pnpm-lock.yaml` is excluded by `!**/pnpm-lock.yaml`
📒 Files selected for processing (2) * apps/web/next.config.js (2 hunks) * apps/web/package.json (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1) * apps/web/next.config.js
🧰 Additional context used
🔇 Additional comments (4)
apps/web/package.json (4)
`15-18`: **Verify the impact of test script changes.** The `test:integration` script has been simplified, and the `test` script that combined unit and e2e tests has been removed. This change aligns with the migration to pnpm but may have implications: 1. The removal of `NODE_ENV=test` from `test:integration` might affect the test environment setup. 2. There's no longer a single command to run both unit and integration tests together. Please ensure these changes don't negatively impact your testing process. Consider: 1. Verifying if `NODE_ENV=test` is set elsewhere for integration tests. 2. Creating a new script that combines `test:unit` and `test:integration` if needed. Run the following script to check: ```shell #!/bin/bash # Description: Verify the changes in test scripts and their usage in CI/CD. # Test 1: Check if NODE_ENV is set elsewhere for integration tests rg --type yaml -i "NODE_ENV.*test.*playwright" # Test 2: Look for any scripts that might be running both unit and integration tests rg --type yaml -i "test:unit.*test:integration|test:integration.*test:unit" ``` This comment reinforces the concerns raised in a previous review about potential issues with test script changes. --- Line range hint `1-113`: **Summary: Approve package.json changes with verification steps.** The changes in this `package.json` file are well-aligned with the PR objective of migrating to pnpm and transitioning to a monorepo structure. Key points: 1. Scripts have been updated, with some simplifications and removals. 2. Dependencies and devDependencies have been updated to use workspace references where appropriate. 3. New packages have been added, and some versions have been updated. Overall, these changes appear to be appropriate and consistent. However, to ensure a smooth transition, please: 1. Verify that all scripts, especially test scripts, work as expected with the new setup. 2. Confirm that all dependencies resolve correctly and don't introduce conflicts. 3. Check that the development environment and build process work smoothly with the updated devDependencies. Once you've completed these verifications, this PR should be ready for merging. --- Line range hint `24-91`: **Approve dependency updates and additions.** The changes in the dependencies section align well with the migration to pnpm and the move to a monorepo structure. Notable changes include: 1. Updated @rallly/* dependencies to use workspace references (e.g., `workspace:*`). 2. Added new dependencies like `@radix-ui/react-select` and `preview-email`. 3. Updated versions for several packages (e.g., `lucide-react`, `next-auth`). These changes are consistent with monorepo best practices and likely introduce new features or fix issues. To ensure these changes don't introduce any conflicts or breaking changes, please: 1. Run `pnpm install` to verify that all dependencies resolve correctly. 2. Execute your test suite to check for any potential issues with the updated packages. You can use the following script to check for any potential conflicts: --- Line range hint `94-111`: **Approve devDependencies updates and additions.** The changes in the devDependencies section are consistent with the migration to pnpm and the monorepo structure. Key changes include: 1. Addition of new devDependencies like `@next/env` and `@types/js-cookie`. 2. Updated @rallly/* devDependencies to use workspace references. 3. Updated version of `vitest` to `^2.1.1`. These changes improve TypeScript support and may introduce new testing features or improvements. To ensure these changes don't introduce any issues in the development environment, please: 1. Verify that all development scripts (e.g., build, lint) work correctly with the updated devDependencies. 2. Check if the new version of vitest introduces any breaking changes that might affect your tests. You can use the following script to verify:
--- Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
❤️ Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
lukevella commented 1 month ago

Couldn't get docker image to work. Got an error saying the prisma engine is missing. I give up.