---
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).

You do not have to use the Headless SSR Proxy for [production deployment](https://doc.sitecore.com/sai/en/developers/jss/22/jss-sai/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).

[Integration with advanced Sitecore editors](https://doc.sitecore.com/sai/en/developers/jss/22/jss-sai/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 Pages does not require a separate deployment and only supports the [HTTP Rendering Engine](https://doc.sitecore.com/xp/en/developers/hd/22/sitecore-headless-development/http-rendering-engine.html).

You do not have to install Node.js on your Content Management server.

You do not have to deploy your application to the Content Management role.

## Development

When developing JSS applications with the Next.js SDK there is less boilerplate code than for other framework-specific 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. The template is optimized for [the development workflow](https://doc.sitecore.com/sai/en/developers/jss/22/jss-sai/development-workflow.html "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`.
- 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 data model (templates), you must update [GraphQL introspection](https://doc.sitecore.com/sai/en/developers/jss/22/jss-sai/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 media requests. Therefore, the Layout Service excludes server URLs.