chore: disable source maps generation

[YounixM]

Summary by CodeRabbit

• New Features

  • Enhanced configuration for production builds to improve performance and security.
  • Introduced options for more granular control over the webpack configuration.

• Improvements

  • Optimized caching strategy to enhance build performance in production environments.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
signoz-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 17, 2024 6:10am

[coderabbitai]

Walkthrough

The changes made to the next.config.js file enhance the configuration of a Next.js application. Key modifications include disabling source maps for production builds and introducing an experimental section for server source maps. The webpack configuration function has been updated to accept additional parameters, allowing for improved control over the build process. A new caching strategy is implemented to optimize performance during production builds. These adjustments collectively focus on refining build performance and flexibility.

Changes

File	Change Summary
next.config.js	- Set productionBrowserSourceMaps to false to disable source maps in production.
	- Introduced experimental section with serverSourceMaps set to false.
	- Updated webpack configuration to include parameters: buildId, dev, isServer, etc.
	- Added conditional caching strategy to use in-memory caching when not in development mode.

Poem

In the code where bunnies hop,
Changes made, we’ll never stop!
Source maps tucked away so neat,
Performance boosts, oh what a treat!
With webpack’s dance, we twirl and play,
Optimized builds, hip-hip-hooray! 🐇✨

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8d6eb3d and d550af3.

Files selected for processing (1)

• next.config.js (2 hunks)

Additional comments not posted (4)

next.config.js (4)

69-69: LGTM!

Disabling source maps in production builds is a good practice to improve performance and security.

---

70-72: LGTM!

Disabling server-side source maps in production is a good practice to optimize performance.

---

239-239: LGTM!

The updated webpack configuration function signature allows for more granular control over the webpack configuration based on the build context.

---

245-249: LGTM!

Modifying the caching strategy to use in-memory caching in non-development environments can enhance build performance.

Warning

Review ran into problems

Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review.

---

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 generate interesting stats about this repository and render them as a table.
  -- @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.

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.

[Calm-Rock]

Closing as discussed with the team.