fix: Vercel deployment (by including WASM files)

[marcusschiesser]

Summary by CodeRabbit

• Bug Fixes

  • Resolved issues related to the "create-llama" functionality during Vercel deployment, improving reliability.

• New Features

  • Updated Next.js configuration to enhance the handling of WebAssembly files in API routes, ensuring proper tracing and inclusion in build output.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0e7f74f

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 update improves the "create-llama" deployment process on Vercel, ensuring a more reliable application deployment. Additionally, the Next.js configuration has been enhanced to include WebAssembly files in the build output, specifically for API routes. These changes work together to streamline deployment and improve the handling of WebAssembly modules in the application.

Changes

File Path	Change Summary
.changeset/lovely-rockets-ring.md	Introduced a patch for "create-llama" addressing Vercel deployment issues.
templates/types/streaming/nextjs/...	Modified next.config.json to include WebAssembly files in output tracing for API routes.

Poem

🐰 In the meadow, dreams take flight,
Deployment dances in the moonlight.
WebAssembly hops with glee,
Next.js shines, as bright as can be.
With every change, the code does sing,
A rabbit's joy, in every spring! 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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, codebase verification and nitpick comments (1)

.changeset/lovely-rockets-ring.md (1)

1-5: Consider providing more details in the changeset message.

The changeset message is quite brief. It would be helpful to include more details about what was fixed in the Vercel deployment.

- Fix Vercel deployment
+ Fix Vercel deployment by including WASM files in the build output for API routes.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8b89ac5 and 0e7f74f.

Files selected for processing (2)

• .changeset/lovely-rockets-ring.md (1 hunks)
• templates/types/streaming/nextjs/next.config.json (1 hunks)

Additional comments not posted (1)

templates/types/streaming/nextjs/next.config.json (1)

4-5: LGTM!

The configuration change correctly includes WebAssembly files for API routes.