Configure front-end frameworks and libraries with Azure Static Web Apps
Article
Azure Static Web Apps requires that you have the appropriate configuration values in the build configuration file for your front-end framework or library.
Configuration
The following table lists the settings for a series of frameworks and libraries1.
The intent of the table columns is explained by the following items:
API artifact location (api location): Lists the value for api_location, which is the folder containing the built managed Azure Functions for frameworks that require server-side hosting.
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.
Note
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.
Build end-to-end solutions in Microsoft Azure to create Azure Functions, implement and manage web apps, develop solutions utilizing Azure storage, and more.