Angular

After playing around with Azure Static Web Apps (ASWA) for some time I found some quirks and gotchas. Of course Static Web Apps are still in preview. Most of these are probably because of that fact. Despite that, it might still be interesting to know about them. That way if you run into any of them, you’ll at least know it’s not you … 😉 🏭 Creating an Azure Static Web App It all starts when you want to create an ASWA: searching for it in the list of resources in the Azure portal doesn’t show it.

Although the two have a lot in common, even including parts of the name, there are a few very clear differences between Static website hosting in Azure Storage and Static Web Apps. We’ll have a look at what those differences are and take a first look at the most recent of the two: Static Web Apps. Static website hosting in Azure Storage Static website hosting is a feature you can enable free of charge on a storage account.

In one of the projects I’m currently working on we’re using an ASP.NET Core Web API with an Angular front-end. We’re using ADAL.js as an Azure Active Directory Authentication Library and ng2-adal for integration with Angular. To get the type declarations for all these packages in TypeScript we use The Future of Declaration Files. Some time ago, our build server started acting up with the following message: Type 'Observable<void>' is not assignable to type 'Observable<User>' The error occured in ADAL.