Skip to main content

Azure Static Web Apps–Introducing the SWA CLI

As a follow-up on the presentation I did at CloudBrew about Azure Static Web Apps I want to write a series of blog posts.

Today I want to introduce you a real piece of magic, the SWA CLI! It brings the full Static Web App experience to your local machine. This means that you can test some of the Static Web App features like authentication without the need to have a Static Web App created and configured in Azure.

Installation

The easiest way to install the SWA CLI is through npm:

npm install -g @azure/static-web-apps-cli

To check if the installation was successful, try to run the swa –version command. The output should look like this:

swa --version
1.1.9

Configuration

To make your web application work with the SWA CLI, you need to provide the necessary configuration details. This can be done by executing swa or swa init from the root folder of your project.

You need to provide some details about the frameworks you are using and some other information. The SWA CLI tries to detect the other details:

The end result is a swa-cli.config.json file. Here is an example file I used during my session at CloudBrew:

Running your application

Last step is to actually run our SWA CLI enabled application. The command to do this is easy to guess swa start. As in our example we have both an Angular application and an API using a Managed Function, both are started:


We can now browse to the emulator URL as seen in the screenshot above…and tadaa!, There we have our Static Web App running completely locally:

Great!

In the next post I’ll share some other features of the SWA CLI and let you look behind the curtain to explain how this all works.

More information

Static Web Apps CLI Documentation | Static Web Apps CLI (azure.github.io)

 

    Popular posts from this blog

    .NET 8–Keyed/Named Services

    A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

    Kubernetes–Limit your environmental impact

    Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...