chore: Fix highlight.js issue with Next.js static build

[leehuwuj]

Summary by CodeRabbit

• Bug Fixes

  • Resolved rendering issues with highlight.js in Next.js static builds, improving compatibility and performance.

• New Features

  • Updated Next.js configuration to include the transpilePackages property for highlight.js, enhancing package processing during builds.

[changeset-bot]

🦋 Changeset detected

Latest commit: d476444

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]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces a patch labeled "create-llama" that resolves an issue with the integration of highlight.js in a Next.js static build. Specifically, it modifies the next.config.json file to include a new property that ensures highlight.js is transpiled during the build process. This change aims to improve compatibility and functionality within a Next.js application configured for static site generation.

Changes

File Path	Change Summary
.changeset/stupid-cougars-raise.md	Introduced patch "create-llama" to fix highlight.js issues in Next.js static builds.
templates/types/streaming/nextjs/next.config.json	Added "transpilePackages": ["highlight.js"] to experimental section.

Possibly related PRs

• fix: simplify webpack config #174: Changes in the Webpack configuration may indirectly relate to the Next.js setup affected by highlight.js.
• fix: Vercel deployment (by including WASM files) #201: Modifications to next.config.json that could impact highlight.js processing in Next.js.
• fix: update nextjs config #262: Updates to next.config.json relevant to highlight.js integration in Next.js.
• fix: vercel ai update crash sending annotations #287: Addresses deployment issues potentially involving highlight.js functionality in a Vercel context.
• fix: bump llama-index-callbacks-arize-phoenix package #340: Update to llama-index-callbacks-arize-phoenix package relating to overall application functionality, including highlight.js.
• fix: enhance performance for codeblock #347: Changes to the CodeBlock component that now uses highlight.js, directly related to the main PR.
• fix: .env not loaded on poetry run generate #348: Fix for loading the .env file that could impact highlight.js operation environment.
• Don't need to run generate script for LlamaCloud #352: Simplifies LlamaCloud process, indirectly relating to the application setup with highlight.js.

Suggested reviewers

• marcusschiesser

🐰 In the meadow, bright and spry,
A patch for Llama, oh my, oh my!
With highlight.js now in tow,
Next.js builds will surely glow.
Hopping through code, we cheer and play,
For smoother renders, hip-hip-hooray! 🌼

---

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.

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.