Skip to content

Commit 1bfbc37

Browse files
authored
Merge pull request #185318 from craigshoemaker/swa/local-dev
[Static Web Apps] Local dev: Add summary paragraph
2 parents 57f1f6a + 3047747 commit 1bfbc37

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

articles/static-web-apps/local-development.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,12 @@ The following chart shows how requests are handled locally.
5353

5454
- **Responses** from all services are returned to the browser as if they were all a single application.
5555

56+
The following article details the steps for running a node-based application, but the process is the same for any language or environment. Once you start the UI and the Azure Functions API apps independently, then start the Static Web Apps CLI and point it to the running apps using the following command:
57+
58+
```console
59+
swa start http://localhost:<DEV-SERVER-PORT-NUMBER> --api-location http://localhost:7071
60+
```
61+
5662
## Prerequisites
5763

5864
- **Existing Azure Static Web Apps site**: If you don't have one, begin with the [vanilla-api](https://github.com/staticwebdev/vanilla-api/generate?return_to=/staticwebdev/vanilla-api/generate) starter app.
@@ -157,7 +163,7 @@ For more information on different debugging scenarios, with guidance on how to c
157163

158164
### Sample debugging configuration
159165

160-
Visual Studio Code uses a file to enable debugging sessions in the editor. If Visual Studio Code doesn't generate a *launch.json* file for you, you can place the the following configuration in *.vscode/launch.json*.
166+
Visual Studio Code uses a file to enable debugging sessions in the editor. If Visual Studio Code doesn't generate a *launch.json* file for you, you can place the following configuration in *.vscode/launch.json*.
161167

162168
```json
163169
{

0 commit comments

Comments
 (0)