connect-react dev ex improvements

[jsendo]

WHY

Summary by CodeRabbit

• Chores
  • Introduced an automated watch mode for development that continuously rebuilds the project during active coding, streamlining the development process.

[vercel]

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

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Feb 19, 2025 9:15pm
pipedream-docs	⬜️ Ignored (Inspect)			Feb 19, 2025 9:15pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Feb 19, 2025 9:15pm

[coderabbitai]

Walkthrough

The pull request adds a new script to the packages/connect-react/package.json file. The new "watch" script is configured to run the Vite build in watch mode with NODE_ENV set to development. This update enables continuous rebuilding during development without affecting any other parts of the file.

Changes

File	Change Summary
packages/connect-react/package.json	Added a new "watch" script: NODE_ENV=development vite build --watch --mode development to the scripts section.

Sequence Diagram(s)

Loading

sequenceDiagram
    participant Dev as Developer
    participant CLI as Command Line
    participant Vite as Vite Build Process

    Dev->>CLI: Run "npm run watch"
    CLI->>CLI: Set NODE_ENV=development
    CLI->>Vite: Start Vite build (--watch, --mode development)
    Vite->>CLI: Watch for file changes and trigger rebuilds

Suggested reviewers

• bzwrk

Poem

I'm a bunny coding under a full moon's gleam,
Hopping through scripts with a developer's dream.
A new "watch" script makes my heart skip a beat,
Building and watching, oh what a treat!
In fields of code, I rush free—happy and fleet! 🐇

---

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/connect-react/package.json (1)

21-22: Enhanced Development Experience with New Watch Script

The addition of the "watch": "NODE_ENV=development vite build --watch --mode development" script enables continuous rebuilding in development mode, which aligns well with the PR objectives. One suggestion is to consider cross-platform compatibility—particularly on Windows—by leveraging a tool like cross-env to set environment variables reliably across different operating systems.

For example, if Windows support is required, you could update the script as follows:

-    "watch": "NODE_ENV=development vite build --watch --mode development"
+    "watch": "cross-env NODE_ENV=development vite build --watch --mode development"

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d89efa3 and 5266e51.

📒 Files selected for processing (1)

• packages/connect-react/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base