cli: include runtime-meta in package

[fracek]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new JSON file has been added to the project, providing metadata for the "apibara" package, including release type, comments, package name, author's email, and dependent change type. Additionally, the package.json for the apibara project has been updated to version 2.0.0-beta.14, with expanded exports fields that include new entries for runtime metadata files and wildcard exports for dynamic resolution. Two new files, runtime-meta.d.ts and runtime-meta.mjs, have also been included in the package distribution.

Changes

File Path	Change Summary
change/apibara-d2c0b8ca-2e3d-4189-91ea-3643281a08a2.json	Added metadata entry for the "apibara" package, indicating a prerelease with runtime metadata and patch dependency.
packages/cli/package.json	Updated version to 2.0.0-beta.14, expanded exports to include new entries for runtime/meta, and added wildcard exports. Included runtime-meta.d.ts and runtime-meta.mjs in the files array.

Possibly related PRs

• indexer: update drizzle and drizzle sink #107: The main PR introduces a new JSON file for package metadata, while PR indexer: update drizzle and drizzle sink #107 also introduces a JSON file for the @apibara/indexer package with similar metadata structure, indicating a related focus on package management and versioning.

Poem

In the meadow where bunnies play,
A new package hops in today!
With metadata shining bright,
It brings us joy, oh what a sight!
Runtime files, a leap ahead,
In our code, new paths are spread! 🐇✨

---

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 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

🧹 Outside diff range and nitpick comments (1)

packages/cli/package.json (1)

58-59: Consider moving runtime-meta files to the dist directory

The new runtime-meta files are placed in the package root, while other compiled files are under the dist/ directory. This inconsistency might make maintenance more difficult.

Consider:

1. Moving these files to dist/runtime/ to maintain consistency
2. Updating the exports paths accordingly

   "files": [
     "dist",
     "src",
-    "runtime-meta.d.ts",
-    "runtime-meta.mjs",
     "README.md"
   ],

And update the exports:

     "./runtime/meta": {
-      "types": "./runtime-meta.d.ts",
-      "import": "./runtime-meta.mjs"
+      "types": "./dist/runtime/meta.d.ts",
+      "import": "./dist/runtime/meta.mjs"
     },

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b7f761d and 3823e4c.

📒 Files selected for processing (2)

• change/apibara-d2c0b8ca-2e3d-4189-91ea-3643281a08a2.json (1 hunks)
• packages/cli/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• change/apibara-d2c0b8ca-2e3d-4189-91ea-3643281a08a2.json

🔇 Additional comments (2)

packages/cli/package.json (2)

Line range hint 1-108: LGTM! The changes align with the PR objectives

The package.json changes successfully implement the runtime-meta inclusion with proper type definitions and module exports. The version bump to 2.0.0-beta.14 is appropriate for these changes.

---

Line range hint 46-56: Review the overlapping wildcard exports configuration

The wildcard exports ./runtime/* and ./dist/runtime/* both resolve to the same destination paths, which could lead to ambiguous module resolution. Consider:

1. Keeping only one wildcard pattern
2. Ensuring clear precedence rules if both patterns are necessary

Let's verify if there are any actual runtime files that would be affected by this: