---
title: "Sitecore JSS for Next.js differences from JSS for React, Angular, and Vue.js"
slug: "sitecore-jss-for-next-js-differences-from-jss-for-react-angular-and-vue-js"
abstract: "How JSS for Next.js is different from JSS for React, Angular, and Vue.js"
---
# Sitecore JSS for Next.js differences from JSS for React, Angular, and Vue.js

The Next.js SDK for Sitecore has some important differences from other Sitecore JavaScript SDKs.

## 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](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/deployment-options-for-jss-next-js-apps.html "Deployment options for JSS Next.js apps") because Next.js natively supports server-side rendering (SSR), as well as SG and incremental static generation, [configuring rewrites, and proxying](https://nextjs.org/docs/api-reference/next.config.js/rewrites#rewriting-to-an-external-url).

You can integrate [Sitecore tracking and analytics in a JSS Next.js app](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/tracking-and-analytics-integration-in-jss-next-js-apps.html "Tracking and analytics integration in JSS Next.js apps") if you use SSR and the Sitecore Layout Service REST API.

[Integration with advanced Sitecore editors](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/architecture-and-apis-for-integrating-jss-next-js-apps-with-sitecore-editors.html "Architecture and APIs for integrating JSS Next.js apps with Sitecore editors"), such as Experience Editor, does not require a separate deployment and only supports the [HTTP Rendering Engine](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/http-rendering-engine.html "HTTP rendering engine").

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.

## Development

When developing JSS applications with JSS for Next.js there is less boilerplate code than for other framework-specific Sitecore JavaScript SDKs.

The Next.js sample has the following characteristics:

- It has a simplified component filesystem structure.
- Because Next.js supports Typescript, the sample app uses Typescript by default.
- It includes code generation for GraphQL schema types.
- It can be created based on a [containerized template](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/the-sitecore-containers-template-for-jss-next-js-apps.html "The Sitecore Containers template for JSS Next.js apps"). The template is optimized for [the Sitecore-first workflow](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/sitecore-first-development-workflow.html "Sitecore-first development workflow").

Specifically, when working with JSS for Next.js remember the following:

- Do not use the JSS CLI commands `jss deploy app` or `jss deploy files`.
- Use `jss deploy items` for [code-first item import](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/code-first-development-workflow.html "Code-first development workflow").
- You do not have to configure a `sitecoreDistPath` in your `package.json` file.
- The `Link` and `RichText` field helper components support client-side routing out of the box.
- If you add `.graphql` files to your solution or make changes to your Sitecore data model (templates), you must update [GraphQL introspection](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/introspecting-the-graphql-schema-in-jss-next-js-apps.html "Introspecting the GraphQL schema in JSS Next.js apps").
- The Next.js app is configured to proxy Sitecore media requests. Therefore, the Layout Service excludes server URLs.