More aggressive file ignore on bundle for Bun and Node

[jhaynie]

Requires agentuity/cli#385

This allows us to essentially say "ignore everything except the directory and file"

Summary by CodeRabbit

• Chores
  • Updated bundling rules to exclude all files by default, with exceptions for specific configuration files and directories. This change streamlines which files are included during bundling.

[coderabbitai]

Walkthrough

The ignore patterns in bundling configuration files were updated. Instead of selectively ignoring specific directories, the new approach ignores all files by default, with explicit exceptions to include only the "/.agentuity/**" directory and the "/agentuity.yaml" file. No changes were made to exported or public entities.

Changes

Files	Change Summary
bunjs/rules.yaml, nodejs/rules.yaml	Updated bundle ignore patterns to ignore all files except "/.agentuity/**" and "/agentuity.yaml".

Poem

In a warren of files, we once picked and chose,
Now we burrow deep where only two paths arose.
All else is ignored, a blanket so wide,
Except agentuity’s secrets, which we never hide.
Hop along, little bundles, neat and precise—
Only what matters, in code rabbit’s device!
🐇✨

---

📜 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 c895e9f and e38c9a2.

📒 Files selected for processing (2)

• bunjs/rules.yaml (1 hunks)
• nodejs/rules.yaml (1 hunks)

🔇 Additional comments (2)

nodejs/rules.yaml (1)

10-12: Verify bundler ignore semantics for negative patterns
Using "**/*" ignores all files, and the negative patterns "!/.agentuity/**" and "!/agentuity.yaml" aim to re-include the agentuity artifacts. Confirm that your bundler supports leading-slash negative globs and that parent directories aren’t inadvertently excluded. You may need to explicitly include the /.agentuity directory itself before its contents.

bunjs/rules.yaml (1)

10-12: Consistent ignore pattern change
This mirrors the update in nodejs/rules.yaml, switching to a blanket ignore with two explicit exceptions. The patterns are consistent and align across both environments.

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Commit Unit Tests in branch js-ignore
• Post Copyable Unit Tests in Comment

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests 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.