feat: add components.json to use CLI

[thucpn]

Tested by try adding a component via CLI. Eg:

pnpm dlx shadcn@latest add avatar

[changeset-bot]

🦋 Changeset detected

Latest commit: 4176d74

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

This PR includes changesets to release 1 package

Name	Type
create-llama	Patch

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 two new configuration files. The first change, detailed in the .changeset/sharp-peas-grow.md patch labeled "create-llama," adds a CLI-related components.json file. The second change adds a Next.js configuration file (components.json) that defines UI component settings including styling options, aliasing, and TypeScript support. Both changes enhance the declarations of public entities by providing structured configuration data for respective environments.

Changes

File(s)	Change Summary
.changeset/sharp-peas-grow.md	Introduces the "create-llama" patch which includes a new components.json for CLI usage.
templates/.../components.json	Adds a Next.js JSON configuration for UI components with schema validation, styling, alias paths, and TSX support.

Suggested reviewers

• marcusschiesser

Poem

In the garden of code, I hop with delight,
New files sprout like carrots, shining bright.
A patch of "create-llama" paves the way,
With config seeds growing day by day.
From CLI to Next.js, joy takes its flight! 🐇✨

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1552eb and 4176d74.

📒 Files selected for processing (2)

• .changeset/sharp-peas-grow.md (1 hunks)
• templates/types/streaming/nextjs/components.json (1 hunks)

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

• .changeset/sharp-peas-grow.md

🧰 Additional context used

📓 Path-based instructions (1)

templates/types/streaming/nextjs/components.json (1)

Pattern templates/**: For files under the templates folder, do not report 'Missing Dependencies Detected' errors.

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

• GitHub Check: typescript (20, 3.11, ubuntu-22.04, express, --llamacloud)
• GitHub Check: typescript (20, 3.11, ubuntu-22.04, express, --example-file)
• GitHub Check: typescript (20, 3.11, ubuntu-22.04, express, --no-files)
• GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --llamacloud)
• GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --example-file)
• GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --no-files)
• GitHub Check: typescript (20, 3.11, windows-latest, express, --llamacloud)
• GitHub Check: typescript (20, 3.11, windows-latest, express, --example-file)
• GitHub Check: typescript (20, 3.11, windows-latest, express, --no-files)
• GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --llamacloud)
• GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --example-file)
• GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --no-files)
• GitHub Check: typescript (20, 3.11, macos-latest, express, --llamacloud)
• GitHub Check: typescript (20, 3.11, macos-latest, express, --example-file)
• GitHub Check: typescript (20, 3.11, macos-latest, express, --no-files)
• GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud)
• GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --example-file)
• GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --no-files)
• GitHub Check: typescript (18, 3.11, ubuntu-22.04, express, --llamacloud)
• GitHub Check: typescript (18, 3.11, ubuntu-22.04, express, --example-file)
• GitHub Check: typescript (18, 3.11, ubuntu-22.04, express, --no-files)
• GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --llamacloud)
• GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --example-file)
• GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --no-files)
• GitHub Check: typescript (18, 3.11, windows-latest, express, --llamacloud)
• GitHub Check: typescript (18, 3.11, windows-latest, express, --example-file)
• GitHub Check: typescript (18, 3.11, windows-latest, express, --no-files)
• GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --llamacloud)
• GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --example-file)
• GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --llamacloud)
• GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --no-files)
• GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --example-file)
• GitHub Check: typescript (18, 3.11, macos-latest, express, --llamacloud)
• GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --no-files)
• GitHub Check: typescript (18, 3.11, macos-latest, express, --example-file)
• GitHub Check: python (20, 3.11, windows-latest, fastapi, --llamacloud)
• GitHub Check: typescript (18, 3.11, macos-latest, express, --no-files)
• GitHub Check: python (20, 3.11, windows-latest, fastapi, --example-file)
• GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --llamacloud)
• GitHub Check: python (20, 3.11, windows-latest, fastapi, --no-files)
• GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --example-file)
• GitHub Check: python (20, 3.11, macos-latest, fastapi, --llamacloud)
• GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --no-files)
• GitHub Check: python (20, 3.11, macos-latest, fastapi, --example-file)
• GitHub Check: python (20, 3.11, macos-latest, fastapi, --no-files)

🔇 Additional comments (4)

templates/types/streaming/nextjs/components.json (4)

1-5: Overall Configuration Setup Looks Good

The JSON file correctly initializes the configuration by defining the schema, style, and feature flags for React Server Components (RSC) and TSX support. Please verify that the referenced $schema URL ("https://ui.shadcn.com/schema.json") is current and maintained by the intended provider.

---

6-12: Tailwind Configuration Block is Clear

The Tailwind CSS settings are well-organized. The paths for the Tailwind configuration file and global CSS file appear appropriate, and the options such as baseColor, cssVariables, and prefix are clearly set. Ensure that these file paths align with your project's directory structure.

---

13-19: Aliases Configuration is Well-Structured

The alias mappings provided for components, utilities, UI, libraries, and hooks improve project maintainability and readability. Double-check that these aliases accurately reflect your directory structure and help streamline your imports in the project.

---

20-21: Icon Library Configuration is Properly Defined

The setting "iconLibrary": "lucide" is straightforward. Ensure that your codebase and build configurations properly integrate this icon library.

---

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.

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.