fix: revert nextjs version

[rodrigopavezi]

Problem

Build it failing on deployment environment

Change

Revert Nextjs version back from 15.x to 14.x

Summary by CodeRabbit

• Chores
  • Downgraded the versions of several dependencies to enhance stability, including @next/third-parties, next, and eslint-config-next.

These updates aim to ensure a smoother user experience by maintaining compatibility and performance.

[coderabbitai]

Walkthrough

The changes in this pull request focus on downgrading specific package dependencies in the package.json file. The versions for @next/third-parties, next, and eslint-config-next have been reduced to maintain compatibility or address issues, reflecting a consistent approach to managing dependency versions. No alterations were made to other sections of the package.json, such as scripts or engines.

Changes

File	Change Summary
package.json	Downgraded @next/third-parties from ^15.0.3 to ^14.1.0, next from ^15.0.3 to ^14.1.0, and eslint-config-next from 14.2.3 to 14.1.0.

Possibly related PRs

• fix: go back to version 0.11.0 because it was never released #77: This PR involves a version downgrade in package.json, similar to the downgrades made in the main PR.
• fix: specify node version #82: Although this PR adds a new engines field, it is still related to changes in package.json, but it does not involve downgrading dependencies like the main PR.

Suggested reviewers

• MantisClone
• aimensahnoun
• sstefdev

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 89aee05 and da09095.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (3 hunks)

🔇 Additional comments (2)

package.json (2)

Line range hint 1-49: Verify dependent packages compatibility.

The project uses several Request Network packages and web3 libraries. Please ensure these packages are compatible with Next.js 14.1.0, particularly:

• @requestnetwork/* packages
• @rainbow-me/rainbowkit
• wagmi and related packages

Let's check for any compatibility issues:

✅ Verification successful

Let me gather more information about the package versions and their compatibility.

---

Based on the gathered information, I can now provide the final response:

Dependencies are compatible with Next.js 14.1.0

• Next.js peer dependency requirements show compatibility with both ^13.0.0 and ^14.0.0
• @rainbow-me/rainbowkit v2.2.1 and wagmi v2.13.3 are the latest major versions, which are compatible with Next.js 14
• All @RequestNetwork packages have Node.js >=18.0.0 requirement, which aligns with the project's Node.js 18.x specification
• No dependency conflicts or warnings were found in the package-lock.json

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for Next.js version requirements in dependencies

# Search for Next.js peer dependency requirements in package-lock.json
echo "Checking peer dependencies..."
fd package-lock.json --exec jq -r '.packages | .[] | select(.peerDependencies.next != null) | "\(.name): requires next \(.peerDependencies.next)"'

Length of output: 256

---

Script:

#!/bin/bash
# Check package versions and their dependencies
echo "Checking @requestnetwork packages dependencies..."
rg -A 5 '"@requestnetwork/[^"]+": "' package-lock.json

echo -e "\nChecking wagmi and rainbowkit dependencies..."
rg -A 5 '"@?wagmi|rainbowkit": "' package-lock.json

echo -e "\nChecking for any dependency conflicts or warnings..."
rg "WARN|ERR.*dependency" package-lock.json

Length of output: 7151

---

15-15: LGTM! Next.js version changes are consistent.

The downgrade of Next.js and related packages to v14.1.0 is consistent across all dependencies:

• @next/third-parties: ^14.1.0
• next: ^14.1.0
• eslint-config-next: 14.1.0

Let's verify the stability and security of Next.js 14.1.0:

Also applies to: 30-30, 44-44

---

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.

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.