chore: upgrate nextJS version to avoid vulnerabilities

[aimensahnoun]

TL;DR

Upgraded Next.js from version 14.2.5 to 14.2.35.

What changed?

This PR updates the Next.js dependency from version 14.2.5 to 14.2.35 in both package.json and package-lock.json files. The update includes changes to all related Next.js packages, including @next/env and various platform-specific SWC packages.

How to test?

1. Pull the changes and run npm install
2. Start the development server with npm run dev
3. Verify that the application loads correctly
4. Test key functionality to ensure nothing was broken by the Next.js update

Why make this change?

This update brings in the latest improvements, bug fixes, and security patches from the Next.js framework. Keeping dependencies up-to-date is important for maintaining application security and stability.

Summary by CodeRabbit

• Chores
  • Updated Next.js dependency to version 14.2.35.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Next.js dependency version updated from 14.2.5 to 14.2.35 in package.json. No functional or structural code changes introduced.

Changes

Cohort / File(s)	Summary
Dependency Update package.json	Next.js version bumped from 14.2.5 to 14.2.35

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Simple version number update with no code logic or configuration structure changes
• Verify compatibility with current project setup if needed

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically identifies the main change: upgrading Next.js to address vulnerabilities. It directly relates to the primary objective of the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 12-12-chore_upgrate_nextjs_version_to_avoid_vulnerabilities

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[aimensahnoun]

• chore: upgrate nextJS version to avoid vulnerabilities #110 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3e7ec7d and a91213f.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*

⚙️ CodeRabbit configuration file

**/*: - Only comment on issues that would block merging — ignore minor or stylistic concerns.

• Restrict feedback to errors, security risks, or functionality-breaking problems.
• Do not post comments on code style, formatting, or non-critical improvements.
• Keep reviews short: flag only issues that make the PR unsafe to merge.
• Limit review comments to 3–5 items maximum, unless additional blockers exist.
• Group similar issues into a single comment instead of posting multiple notes.
• Skip repetition — if a pattern repeats, mention it once at a summary level only.
• Do not add general suggestions; focus strictly on merge-blocking concerns.
• If there are no critical problems, respond with minimal approval (e.g., 'Looks good'). Do not add additional review.
• Avoid line-by-line commentary unless it highlights a critical bug or security hole.
• Highlight only issues that could cause runtime errors, data loss, or severe maintainability issues.
• Ignore minor optimization opportunities — focus solely on correctness and safety.
• Provide a top-level summary of critical blockers rather than detailed per-line notes.
• Comment only when the issue must be resolved before merge — otherwise, remain silent.
• When in doubt, err on the side of fewer comments — brevity and blocking issues only.
• Avoid posting any refactoring issues

Files:

• package.json

[greptile-apps]

Greptile Overview

Greptile Summary

This PR attempts to upgrade Next.js from 14.2.5 to 14.2.35 but contains a critical version mismatch in package-lock.json.

Critical Issues:

• The main next package is at version 14.2.35, but all platform-specific SWC binaries (@next/swc-*) are at 14.2.33
• This version mismatch will cause runtime failures when Next.js attempts to load the SWC compiler
• The @next/env package is correctly at 14.2.35, but the dependency resolution for SWC binaries appears to have failed

Resolution Required:

• Delete node_modules and package-lock.json
• Run npm install next@14.2.35 to regenerate the lock file with matching versions
• Verify all @next/* packages are at 14.2.35 before committing

Confidence Score: 0/5

• This PR will cause application crashes and must not be merged
• Score reflects critical version mismatch between Next.js core (14.2.35) and SWC binaries (14.2.33) that will cause immediate runtime failures
• package-lock.json requires complete regeneration with correct dependency resolution

Important Files Changed

File Analysis

Filename	Score	Overview
package.json	4/5	Updated next from 14.2.5 to 14.2.35 - straightforward version bump
package-lock.json	1/5	Version mismatch: next package at 14.2.35 but SWC binaries at 14.2.33 - will cause runtime errors

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant NPM as npm install
    participant Registry as npm Registry
    participant Next as next (14.2.35)
    participant Env as @next/env
    participant SWC as SWC Binaries

    Dev->>NPM: npm install next@14.2.35
    NPM->>Registry: Request next@14.2.35
    Registry->>NPM: Return next package
    NPM->>Registry: Request @next/env@14.2.35
    Registry->>NPM: Return @next/env package
    NPM->>Registry: Request platform-specific SWC binaries
    Note over NPM,Registry: Issue: Returns 14.2.33 instead of 14.2.35
    Registry->>NPM: Return @next/swc-*@14.2.33
    NPM->>Dev: Installation complete (with mismatched versions)
    
    Dev->>Next: npm run dev/build
    Next->>Env: Load environment config (14.2.35)
    Next->>SWC: Load SWC compiler (expects 14.2.35)
    SWC-->>Next: Version mismatch error (14.2.33 ≠ 14.2.35)
    Next-->>Dev: Runtime failure

Loading

[greptile-apps]

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}