You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of starting a dev server separately, you can provide the startup command to the CLI.
57
57
@@ -75,7 +75,7 @@ Then access the application with the emulated services from `http://localhost:42
75
75
76
76
If your project includes API functions, the CLI will check if the Azure Functions Core Tools are installed and available. If not, the CLI will download and install the right version of the Azure Functions Core Tools.
77
77
78
-
#### Start the API server automatically
78
+
#### Start the local API server automatically
79
79
80
80
Run the CLI and provide the folder that contains the API backend (a valid Azure Functions App project):
When developing your backend locally, sometimes it's useful to run Azure Functions Core Tools separately to serve your API. This allows you to use built-in features like debugging and rich editor support.
93
93
@@ -100,6 +100,14 @@ To use the CLI with your local API backend dev server, follow these two steps:
SWA CLI supports connecting to APIs hosted remotely, using services such as Azure and AWS. You can also connect to APIs hosted in a debug session in a GitHub Codespace.
0 commit comments