chore(deps): Upgrade dependencies and development tools

[carhartlewis]

• Update Next.js to version 15.2.0 across all apps
• Upgrade Turbo to version 2.4.4
• Update AWS SDK packages to version 3.758.0
• Bump React and React DOM type definitions
• Add NODE_OPTIONS='--inspect' to dev scripts for easier debugging
• Add resolution overrides for React type definitions

Summary by CodeRabbit

• Chores
  • Upgraded the core web framework to the latest minor version to support enhanced performance and stability.
  • Enhanced development scripts with debugging support, enabling inspection during development.
  • Updated several dependencies to ensure consistency and reduce potential conflicts.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
app	❌ Failed (Inspect)			Feb 28, 2025 2:11pm
comp-portal	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 28, 2025 2:11pm
web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 28, 2025 2:11pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates multiple package.json files across the project. In three app directories, the development script now prepends NODE_OPTIONS='--inspect' to enable debugging, and the Next.js version is upgraded to ^15.2.0. Additionally, the apps/app/package.json file updates React type definitions in devDependencies and adds a resolutions field to enforce specific versions. The root package.json also sees minor dependency version bumps for packages like turbo, @aws-sdk/client-s3, and @nangohq/node.

Changes

File(s)	Change Summary
apps/app/package.json	Updated dev script with NODE_OPTIONS='--inspect'; upgraded next version to ^15.2.0; updated React type definitions (@types/react and @types/react-dom) in devDependencies; added resolutions for React types.
apps/portal/package.json and apps/web/package.json	Updated dev script to include NODE_OPTIONS='--inspect'; upgraded next version from 15.1.7/^15.1.7 to ^15.2.0.
package.json (root)	Upgraded dependency versions: turbo from ^2.4.2 to ^2.4.4, @aws-sdk/client-s3 from ^3.750.0 to ^3.758.0, and @nangohq/node from ^0.53.1 to ^0.53.2.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Terminal
    participant NextServer
    participant Debugger
    Developer->>Terminal: Execute "dev" command (with NODE_OPTIONS='--inspect')
    Terminal->>NextServer: Start Next.js server with debug flag
    NextServer->>Debugger: Open debug connection on inspector port
    Debugger-->>Developer: Establish debugging session

Loading

Poem

I'm a rabbit, hopping through the code,
Discovering updates in every node.
Scripts now shine with a debugging glow,
Next.js versions hop high and slow.
With type fixes and resolutions in sight,
I celebrate these changes with delight!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 72a63b5 and 774bcbc.

⛔ Files ignored due to path filters (2)

• bun.lock is excluded by !**/*.lock
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (2)

• apps/app/package.json (3 hunks)
• package.json (2 hunks)

---

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 generate docstrings to generate docstrings for this 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.