Fix bun detection, dev flushing, and init command

[nicktrn]

The init command will now install packages locked to the exact CLI version. Additionally, the correct (v4-)latest tag will be displayed in the next steps section.

Summary by CodeRabbit

• New Features

  • The default installation behavior now installs the "v4-beta" package, offering early access to upcoming functionality.

• Bug Fixes

  • Improved trigger configuration and entry-point validation for smoother initialization.
  • Enhanced error handling and logging during development flush operations.
  • Updated support for test-based dependency lock files.

• Chores

  • Upgraded a key dependency to boost overall stability and performance.

[changeset-bot]

🦋 Changeset detected

Latest commit: 8d6d4ff

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

This pull request introduces several updates to the "trigger.dev" functionality. It includes new changeset files that document patches for custom trigger directories, installation command defaults, dependency management for testing, and improved flush error handling. Additionally, the dependency version in the CLI package is upgraded, the entry point validation logic now employs absolute path resolution with updated imports, the default package tag in the init command is modified to reflect the current CLI version, and the flush operation in the worker module is enhanced by switching from Promise.all to Promise.allSettled.

Changes

File(s)	Change Summary
.changeset/{late-chairs-ring, moody-squids-count, polite-lies-fix, shiny-kiwis-beam}.md	New changeset files documenting patches for "trigger.dev", addressing custom trigger directories, installation command version, test-based bun.lock support, and graceful flush error handling.
packages/cli-v3/package.json	Upgraded nypm dependency from ^0.3.9 to ^0.5.4.
packages/cli-v3/src/build/bundle.ts	Updated isInitEntryPoint logic to use absolute paths with resolve and added basename and dirname to the import statement.
packages/cli-v3/src/commands/init.ts	Changed default tag option from "latest" to a dynamic value based on the current CLI version in both the option definition and command configuration.
packages/cli-v3/src/entryPoints/dev-run-worker.ts	Revised the flushAll function to use Promise.allSettled for handling flush operations, with enhanced logging and updated return types for flush functions.

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant CLI
  participant InitCommand
  participant BundleChecker
  User->>CLI: Run init command (with dynamic tag)
  CLI->>InitCommand: Execute command with options
  InitCommand->>BundleChecker: Validate init entry point using absolute paths
  BundleChecker-->>InitCommand: Return validation result
  InitCommand-->>CLI: Complete initialization

Loading

sequenceDiagram
  participant Worker
  participant TracingSDK
  participant Metadata
  Worker->>TracingSDK: Initiate flush (timeout)
  Worker->>Metadata: Initiate flush (timeout)
  TracingSDK-->>Worker: Return flush result
  Metadata-->>Worker: Return flush result
  Worker->>Worker: Process results via Promise.allSettled
  Worker-->>Worker: Log successes and errors

Loading

Poem

I hop through code with joyful flair,
Patching bits with careful care.
Trigger.dev tweaks now align,
From init checks to flush design,
I wiggle my ears in merry air! 🐇

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 217fdee and 8d6d4ff.

📒 Files selected for processing (1)

• packages/cli-v3/src/commands/init.ts (3 hunks)

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

• packages/cli-v3/src/commands/init.ts

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

• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: units / 🧪 Unit Tests
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)

---

🪧 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 plan to trigger planning for file edits and PR creation.
• @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.