fix: update nextjs config

[thucpn]

Summary by CodeRabbit

• New Features

  • Updated the llamaindex dependency to version 0.5.20, which may include performance improvements and minor feature enhancements.
  • Introduced granular control over file tracing in the build process, allowing for better management of included and excluded files.

• Bug Fixes

  • Minor fixes and improvements associated with the updated llamaindex version.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4d70187

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The changes include a minor version upgrade of the llamaindex dependency from 0.5.19 to 0.5.20 in both Next.js and Express template configurations. Additionally, the Next.js configuration file has been updated to include a new section for outputFileTracingExcludes, enhancing control over file inclusion during the build process.

Changes

File	Change Summary
.../express/package.json	Updated llamaindex from 0.5.19 to 0.5.20 (minor version upgrade).
.../nextjs/next.config.json	Added outputFileTracingExcludes section to control included files during the build process.
.../nextjs/package.json	Updated llamaindex from 0.5.19 to 0.5.20 (minor version upgrade).

Possibly related issues

• Update nextjs-llama3 community template to use latest LlamaIndexTS #78: This issue mentions errors when using an earlier version of llamaindex. The upgrade to 0.5.20 may address compatibility issues and improve stability.

Poem

🐇 In the meadow, changes bloom,
A version lift dispels the gloom.
With tracing files, we set the pace,
New paths we carve in coding space.
Hops of joy, let’s celebrate,
For every fix, we elevate! 🌼

---

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9039840 and 4d70187.

Files selected for processing (3)

• templates/types/streaming/express/package.json (1 hunks)
• templates/types/streaming/nextjs/next.config.json (1 hunks)
• templates/types/streaming/nextjs/package.json (1 hunks)

Files skipped from review due to trivial changes (2)

• templates/types/streaming/express/package.json
• templates/types/streaming/nextjs/package.json

Additional comments not posted (1)

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

6-12: Review of outputFileTracingExcludes Configuration

The addition of the outputFileTracingExcludes section in the Next.js configuration file is a significant enhancement for controlling file inclusion during the build process. This configuration aims to exclude files from specific paths such as /api/files/*, .next, node_modules, public, and app. This is a strategic move to improve build efficiency by avoiding unnecessary file processing.

Observations:

• The syntax for the JSON configuration appears correct.
• The paths specified use glob patterns which are appropriate for matching directories and their subdirectories.

Recommendations:

• Ensure that the paths specified do not inadvertently exclude files necessary for the build or runtime.
• It might be beneficial to add comments or documentation within the project to explain the rationale behind excluding these specific directories, especially for new team members or external contributors.

The changes are syntactically correct and align with the objectives outlined in the PR.