Closed leehuwuj closed 2 weeks ago
Latest commit: d476444861589677c8f8b2616237fa1470895db8
The changes in this PR will be included in the next version bump.
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
[!CAUTION]
Review failed
The pull request is closed.
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.
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. |
next.config.json
that could impact highlight.js processing in Next.js.next.config.json
relevant to highlight.js integration in Next.js.llama-index-callbacks-arize-phoenix
package relating to overall application functionality, including highlight.js.CodeBlock
component that now uses highlight.js, directly related to the main PR..env
file that could impact highlight.js operation environment.🐰 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?
Summary by CodeRabbit
Bug Fixes
New Features
transpilePackages
property for highlight.js, enhancing package processing during builds.