Skip to content

fix(example): update nextjs example dependencies to latest versions - #313

Merged
amondnet merged 1 commit into
masterfrom
amondnet/wakeful-matrix
Mar 26, 2026
Merged

fix(example): update nextjs example dependencies to latest versions#313
amondnet merged 1 commit into
masterfrom
amondnet/wakeful-matrix

Conversation

@amondnet

Copy link
Copy Markdown
Owner

Summary

  • Update Next.js example dependencies to latest versions to fix CI build failure
  • Vercel CLI 25.x doesn't support Node.js 22+, causing vercel build to fail with "Found invalid Node.js Version: 22.x"
  • Updated: next 12→16, react 18→19, react-dom 18→19, eslint 8→9, eslint-config-next 12→16, vercel 25→41

Test plan

  • pnpm run lint passes
  • pnpm test passes
  • next build succeeds in example/nextjs
  • CI workflow example-nextjs passes

Update next.js from 12.x to 16.x, React from 18.x to 19.x,
ESLint from 8.x to 9.x, and Vercel CLI from 25.x to 41.x.
This fixes the CI build failure caused by Vercel CLI 25.x not
supporting Node.js 22+.
Copilot AI review requested due to automatic review settings March 26, 2026 07:09
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating the dependencies within the Next.js example application to their most recent versions. The primary motivation for these updates is to rectify existing CI build failures, specifically those arising from compatibility issues between older Vercel CLI versions and newer Node.js environments, ensuring the example remains functional and buildable.

Highlights

  • Dependency Updates: Updated the Next.js example dependencies to their latest versions, including next, react, react-dom, vercel, eslint, and eslint-config-next.
  • CI Build Fix: Resolved continuous integration build failures caused by an incompatibility between Vercel CLI 25.x and Node.js 22+ by upgrading the Vercel CLI.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions

Copy link
Copy Markdown
Contributor

Deploy preview for team-scope-test ready!

✅ Preview
https://team-scope-test-45jfogtul-dietfriends.vercel.app

Built with commit e6b0698.
This pull request is being automatically deployed with vercel-action

@sonarqubecloud

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown
Contributor

Deploy preview for express-basic-auth ready!

✅ Preview
https://express-basic-auth-q0rlf1xwu-minsu-lees-projects-b1e388b7.vercel.app

Built with commit e6b0698.
This pull request is being automatically deployed with vercel-action

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates several dependencies in example/nextjs/package.json, including next, react, react-dom, vercel, eslint, and eslint-config-next. A critical issue was identified where several of the specified dependency versions, such as next 16.2.1 and react 19.2.4, are invalid and do not exist on the public npm registry, which will prevent pnpm install from succeeding. The author needs to verify and correct these dependency versions.

Comment thread example/nextjs/package.json

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Requires human review: Major version updates for Next.js and React, along with significant lockfile changes, require human review to ensure compatibility and correct behavior.

Architecture diagram
sequenceDiagram
    participant Dev as Developer / CI
    participant CLI as Vercel CLI (v41)
    participant Node as Node.js Runtime (v22)
    participant Next as Next.js (v16)
    participant React as React (v19)
    participant Browser as Client Browser

    Note over Dev,Node: Build Time Flow (Fixed Build Failure)

    Dev->>CLI: Run "vercel build"
    CLI->>Node: CHANGED: Check Node.js version compatibility
    
    alt Node version >= 22
        Node-->>CLI: Success: Supported by Vercel CLI 41.x
    else Node version < 22 (Previous State)
        Node-->>CLI: Error: "Found invalid Node.js Version"
    end

    CLI->>Next: Execute "next build"
    Next->>Next: Compile Application Code
    Next->>React: NEW: Render components using React 19 APIs
    React-->>Next: Generated Static/Server Assets
    Next-->>CLI: Build Bundle
    CLI-->>Dev: Deployment Ready

    Note over Next,Browser: Runtime Request Flow

    Browser->>Next: Request Page / Route
    Next->>Next: Resolve Server Components / Middleware
    Next->>React: NEW: Perform Server-Side Rendering (React 19)
    React-->>Next: HTML / RSC Payload
    Next-->>Browser: Send Response

    loop Client Hydration
        Browser->>React: NEW: Hydrate DOM with React 19
        Note right of React: Improved hydration & form actions
    end
Loading

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Next.js example to modern dependency versions so the example-nextjs CI job can build under the repo’s current Node.js runtime (Node 24) and newer Vercel CLI requirements.

Changes:

  • Bumps Next.js example runtime deps: next → 16.2.1, react/react-dom → 19.2.4, vercel → ^41.1.4
  • Updates Next.js example lint tooling: eslint → 9.34.0, eslint-config-next → 16.2.1
  • Regenerates pnpm-lock.yaml to reflect updated dependency graph

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
pnpm-lock.yaml Locks updated Next.js/React/Vercel/ESLint dependency tree for reproducible installs/builds.
example/nextjs/package.json Updates Next.js example dependencies/devDependencies to versions compatible with current CI Node runtime.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@amondnet
amondnet merged commit 1043003 into master Mar 26, 2026
13 of 18 checks passed
@amondnet
amondnet deleted the amondnet/wakeful-matrix branch March 26, 2026 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants