chore: add onComplete callback to options

[joshunrau]

Summary by CodeRabbit

• New Features

  • Introduced an optional callback in the build configuration that allows you to specify custom actions after a build completes.

• Bug Fixes

  • Enhanced error handling during the post-build process so that any issues in the custom callback are properly caught and reported.

[coderabbitai]

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 25 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c87df97 and b176655.

📒 Files selected for processing (4)

• src/meta/__tests__/build.test.ts (5 hunks)
• src/meta/build.ts (1 hunks)
• src/meta/load.ts (1 hunks)
• src/user-config.ts (1 hunks)

Walkthrough

The changes centralize the testing mock and introduce an optional completion callback. In the test suite, an esbuildMock replaces the inline mock for esbuild.build, and tests are updated accordingly, including a new case for error handling in the onComplete callback. In the build process (build.ts), the bundling result is stored, and if an onComplete callback is provided, it is executed with proper error handling. Lastly, configuration files (load.ts and user-config.ts) are updated to include an optional onComplete property for user-defined post-build actions.

Changes

File(s)	Change Summary
src/meta/__tests__/build.test.ts	Introduced a new mock object esbuildMock for the esbuild.build method; updated tests to use esbuildMock.build uniformly; added a test case to verify error handling in the onComplete callback.
src/meta/build.ts	Modified buildProd to store the bundling result and, if provided, execute the onComplete callback asynchronously. Errors thrown in the callback are caught and wrapped in a RuntimeException.
src/meta/load.ts, src/user-config.ts	Added an optional onComplete property to the build configuration schema and type definition, enabling a user-defined callback upon build completion.

Sequence Diagram(s)

sequenceDiagram
    participant Client as Client
    participant BuildProd as buildProd()
    participant Bundle as bundle()
    participant OnComplete as onComplete()

    Client->>BuildProd: Call buildProd(config)
    BuildProd->>Bundle: Execute bundling
    Bundle-->>BuildProd: Return bundleResult
    alt onComplete exists
        BuildProd->>OnComplete: Invoke onComplete callback
        OnComplete-->>BuildProd: Return result / throw error
        BuildProd->>BuildProd: Handle callback result or error (wrap error if thrown)
    end
    BuildProd->>Client: Return final build result

Loading

Poem

Hi there, I'm Bunny, hopping around in code,
Mocks and callbacks in a joyful new mode.
With error handling tight and tests all in line,
I celebrate each change—simply divine!
Hurray for smooth builds and clever, neat tweaks!
🐰✨ Happy coding, with bunny leaps and squeaks!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.

[github-actions]

🎉 This PR is included in version 2.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀