Skip to content

Commit 90ab06b

Browse files
next.js unsupported include
1 parent c6b8803 commit 90ab06b

File tree

3 files changed

+26
-13
lines changed

3 files changed

+26
-13
lines changed

articles/static-web-apps/deploy-nextjs-hybrid.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ In this tutorial, you learn to deploy a [Next.js](https://nextjs.org) website to
2222
- [Node.js](https://nodejs.org) installed.
2323
- [Next.js CLI](https://nextjs.org/docs/getting-started) installed. Refer to the [Next.js Getting Started guide](https://nextjs.org/docs/getting-started) for details.
2424

25+
[!INCLUDE [Unsupported Next.js features](../../includes/static-web-apps-nextjs-unsupported.md)]
26+
2527
## Set up a Next.js app
2628

2729
Begin by initializing a new Next.js application.

articles/static-web-apps/nextjs.md

Lines changed: 3 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,9 @@ ms.date: 10/12/2022
99
ms.author: aapowell
1010
ms.custom: devx-track-js
1111
---
12+
1213
# Deploy Next.js websites on Azure Static Web Apps
14+
1315
Next.js support on Azure Static Web Apps can be categorized as two deployment models, [Static HTML Export](https://nextjs.org/docs/advanced-features/static-html-export) Next.js applications, and _hybrid_ rendering, which covers [Server-Side Rendering](https://nextjs.org/docs/advanced-features/react-18/streaming) and [Incremental Static Regeneration](https://nextjs.org/docs/basic-features/data-fetching/incremental-static-regeneration).
1416

1517
## Static HTML export
@@ -65,16 +67,4 @@ Key features that are available in the preview are:
6567
6668
Follow the [deploy hybrid Next.js applications](deploy-nextjs-hybrid.md) tutorial to learn how to deploy a hybrid Next.js application to Azure.
6769
68-
### Unsupported features in preview
69-
70-
During the preview, the following features of Static Web Apps are unsupported for Next.js with server-side rendering:
71-
72-
- APIs using Azure Functions, Azure AppService, Azure Container Apps or Azure API Management.
73-
- Deployment via the SWA CLI.
74-
75-
- Static Web Apps provided Authentication and Authorization.
76-
- Instead, you can use the Next.js [Authentication](https://nextjs.org/docs/authentication) feature.
77-
- The `staticwebapps.config.json` file.
78-
- Features such as custom headers and routing can be controlled using the `next.config.js` file.
79-
- `skip_app_build` and `skip_api_build` can't be used.
80-
- The maximum app size for the hybrid Next.js application is 100 MB. Consider using Static HTML exported Next.js apps if your requirement is more than 100 MB.
70+
[!INCLUDE [Unsupported Next.js features](../../includes/static-web-apps-nextjs-unsupported.md)]
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
author: craigshoemaker
3+
ms.service: static-web-apps
4+
ms.topic: include
5+
ms.date: 10/26/2022
6+
ms.author: cshoe
7+
---
8+
9+
### Unsupported features in preview
10+
11+
During the preview, the following features of Static Web Apps are unsupported for Next.js with server-side rendering:
12+
13+
- APIs using Azure Functions, Azure AppService, Azure Container Apps or Azure API Management.
14+
- Deployment via the SWA CLI.
15+
16+
- Static Web Apps provided Authentication and Authorization.
17+
- Instead, you can use the Next.js [Authentication](https://nextjs.org/docs/authentication) feature.
18+
- The `staticwebapps.config.json` file.
19+
- Features such as custom headers and routing can be controlled using the `next.config.js` file.
20+
- `skip_app_build` and `skip_api_build` can't be used.
21+
- The maximum app size for the hybrid Next.js application is 100 MB. Consider using Static HTML exported Next.js apps if your requirement is more than 100 MB.

0 commit comments

Comments
 (0)