Sitecore JSS for Next.js differences from JSS for React, Angular, and Vue.js
Architecture and deployment
Next.js provides built-in options for build time and runtime static generation (SG).
Out of the box, the Next.js SDK does not support Sitecore tracking or personalization with SG or Sitecore Experience Edge for XM.
You do not have to use the Headless SSR Proxy for production deployment because Next.js natively supports server-side rendering (SSR), as well as SG and incremental static generation, configuring rewrites, and proxying.
You can integrate Sitecore tracking and analytics in a JSS Next.js app if you use SSR and the Sitecore Layout Service REST API.
You do not have to install Node.js on your Sitecore Content Management server.
You do not have to deploy your application to the Sitecore Content Management role.
The Next.js sample has the following characteristics:
Specifically, when working with JSS for Next.js remember the following:
Do not use the JSS CLI commands
jss deploy appor
jss deploy files.
jss deploy itemsfor code-first item import.
You do not have to configure a
RichTextfield helper components support client-side routing out of the box.
If you add
.graphqlfiles to your solution or make changes to your Sitecore data model (templates), you must update GraphQL introspection.
The Next.js app is configured to proxy Sitecore media requests. Therefore, the Layout Service excludes server URLs.