Feat/migrate to pnpn

[pkspyder007]

✨ Codu Pull Request 💻

Fixes #(issue)

Pull Request details

• INFO ABOUT YOUR PULL REQUEST GOES HERE (Please be as descriptive as possible) 🤜
• Use bullet points to make it easy to read.

Any Breaking changes

• IF ANYTHING YOU'RE COMMITTING WOULD BREAK SOMETHING, INCLUDE HERE WHAT WOULD BREAK
• IF YOU HAVE NO BREAKING CHANGES, ENTER 'None'

Associated Screenshots

• IF YOU HAVE ANY SCREENSHOTS, INCLUDE THEM HERE. ( Welcome file extensions include gifs/png screenshots of your feature in action )
• IF YOU HAVE NO SCREENSHOTS, ENTER 'None'

[Optional] What gif best describes this PR or how it makes you feel

• HERES HOW TO EASILY ADD GIFS TO A PR
• IF NO GIF COMES TO MIND, ENTER 'None'

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
codu	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 11, 2024 10:09pm

[coderabbitai[bot]]

Walkthrough

The pull request introduces changes across multiple files to transition the project from using npm to pnpm as the package manager. The Dockerfile has been updated to install pnpm and modify dependency installation commands accordingly. Documentation files, including README.md and E2E Overview.md, reflect these changes by updating commands and adding new environment variables for end-to-end testing. The setup.sh script has also been modified to use pnpm commands. Overall, the changes aim to streamline dependency management and enhance the clarity of setup instructions.

Changes

File	Change Summary
Dockerfile	Updated to use pnpm for dependency management; changed commands for installing dependencies and building the application.
E2E Overview.md	Updated commands for database seeding to use pnpm; added new environment variables for E2E users.
README.md	Replaced npm commands with pnpm for installation, database migration, and seeding instructions.
setup.sh	Modified terminal commands to use pnpm instead of npm for database operations and development server.

Possibly related PRs

• #1061: Changes in README.md regarding the transition from npm to pnpm for database operations align with the main PR's focus on adopting pnpm in the Dockerfile.
• #1151: Updates README.md and setup.sh to reflect changes in database commands, relevant to the overall transition in dependency management.
• #1181: Modifications regarding user authentication in E2E tests relate to the main PR's updates on command and dependency management.
• #1182: Introduces multiple user support in E2E tests, building upon the main PR's changes in dependency management.
• #1183: Addition of tests for replying to comments in E2E tests continues the work on user interactions relevant to the main PR.
• #1189: Migration of E2E environment variables to constants aligns with the main PR's focus on improving dependency and configuration management.
• #1192: Focus on isolating the E2E test suite from the seed script complements the main PR's changes by enhancing modularity in the testing setup.

Suggested labels

hacktoberfest-accepted, hacktoberfest

🐇 In the garden, we hop and play,
With pnpm here, we clear the way.
Dependencies fresh, commands so neat,
Our setup's now a joyful treat!
So gather 'round, let's cheer and sing,
For smoother builds and the joy they bring! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7dbacddc6b0e8af4a98e5e5c301b8d72089813b2 and 16fc3de2ff04f9727d717bb458cdf960f5416986.

⛔ Files ignored due to path filters (2)

• .github/workflows/e2e-tests.yml is excluded by !**/*.yml
• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml, !**/*.yaml

📒 Files selected for processing (1)

• E2E Overview.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• E2E Overview.md

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[JohnAllenTech]

Going to take this for a spin tonight. Excited to try pnpm its my first time

[JohnAllenTech]

Wow wild how seamless this change was!

Literally just swapped out pnpm for npm for what I already use.

Everything seems to be working. My only concern (and perhaps its not even valid) is this is another step that new contributors will need to do (Installing pnpm). Npm as you know comes bundled with Node so its just one less thing to think about.

Overall I hope this gets approved.

[github-actions[bot]]

Uh oh! @JohnAllenTech, the image you shared is missing helpful alt text. Check https://github.com/codu-code/codu/pull/1188#issuecomment-2453301268.

Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.

Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.

[github-actions[bot]]

Uh oh! @JohnAllenTech, the image you shared is missing helpful alt text. Check https://github.com/codu-code/codu/pull/1188#issuecomment-2453301268.

Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.

Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.