Skip to content

Commit ba1e9c6

Browse files
Update front-end-frameworks.md
1 parent ac9b8da commit ba1e9c6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/static-web-apps/front-end-frameworks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: static-web-apps
55
author: craigshoemaker
66
ms.service: static-web-apps
77
ms.topic: conceptual
8-
ms.date: 07/18/2020
8+
ms.date: 06/24/2024
99
ms.author: cshoe
1010
---
1111

@@ -24,7 +24,7 @@ The intent of the table columns is explained by the following items:
2424
- **Custom build command**: When the framework requires a command different from `npm run build` or `npm run azure:build`, you can define a [custom build command](build-configuration.md#custom-build-commands).
2525

2626
> [!NOTE]
27-
> Some web frameworks that feature server-side rendering and can be deployed to Azure Static Web Apps. This means your app is built into static assets and Azure Functions files. In the configuration file, the static assets are mapped to the *output location* and the Azure Functions files map to the *API artifact location*.
27+
> Some web frameworks that feature server-side rendering and can be deployed to Azure Static Web Apps. This means your app is built into static assets along with Azure Functions. In the configuration file, the static assets are mapped to the *output location* and the Azure Functions files map to the *API artifact location*.
2828
2929
| Framework | Output location (App artifact location) | API artifact location | Custom build command |
3030
|--|--|--|--|

0 commit comments

Comments
 (0)