Replies: 6 comments 2 replies
-
We don't want to develop the CSR project again because both are React technologies with the same functional pages, so there's no need to maintain two sets of projects |
Beta Was this translation helpful? Give feedback.
-
@timneutkens @Timer hi,boss, Do you have any ideas |
Beta Was this translation helpful? Give feedback.
-
Since your project already uses SSR for SEO, you might consider keeping the SSR pages for SEO-critical routes while converting non-critical pages or parts of your app to CSR. This lets you maintain SEO benefits where needed, yet offload the rest to CSR for faster client-side transitions. |
Beta Was this translation helpful? Give feedback.
-
@imrashidov However, our requirement is to convert the SSR pages to CSR as well. All pages of the project are SSR, and we now want to package them into a set of CSR, but we don't want to redevelop the project |
Beta Was this translation helpful? Give feedback.
-
@imrashidov I don't understand what you mean, but what I'm thinking is that after I package it as a CSR project, I don't need to start any services to run the Next project. I just want it to be a very pure single page application after packaging. |
Beta Was this translation helpful? Give feedback.
-
@imrashidov I don't want it to continue using node servers for hosting and PM2 management. I just think it's a regular React project packaged as a single page application |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-Goals
Background
Our project has implemented SSR for SEO, and now we want to continue packaging it as CSR
Proposal
I don't know either
Beta Was this translation helpful? Give feedback.
All reactions