Skip to content

fix(react): nextjs base branch #1981

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SpaNb4 merged 1 commit into from
Jun 12, 2026
Merged

fix(react): nextjs base branch #1981

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions react/modules/tasks/nextjs-ssr-ssg.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Note: You may also use the experimental `vinext` framework for this task. It is

## Technical requirements

1. Create a separate branch for this task from the previous branch task. Branch name: "nextjs-ssr".
1. Create a separate branch for this task from the `api-queries` branch (the branch with your search/API application). Branch name: "nextjs-ssr".
2. Next.js App Router Integration:
- [Migrate your application from vite to the Next.js by using App Router](https://nextjs.org/docs/app/guides/migrating/from-vite).
- React-router should be removed. You must use file-based routing provided by next.js (App Router).
Expand Down Expand Up @@ -193,8 +193,8 @@ Note: You may also use the experimental `vinext` framework for this task. It is

### ❓ Do I need to rewrite the project from scratch or migrate?

You should continue working in the same project and **migrate it** to Next.js App Router.
Create a new branch `nextjs-ssr`, replace `react-router` with file-based routing, and adjust the existing functionality so it works in the new environment — keeping everything from previous modules that doesn’t conflict with the new requirements.
You should continue working on your search/API application and **migrate it** to Next.js App Router.
Branch off `api-queries`, name the new branch `nextjs-ssr`, replace `react-router` with file-based routing, and adjust the existing functionality so it works in the new environment — keeping everything from previous modules that doesn’t conflict with the new requirements (the standalone forms module is excluded).

### ❓ Where should I deploy? Is GitHub Pages allowed?

Expand Down
Loading