I've just been given a project from one of my clients to effectively completely rewrite an old ASP.NET website from over a decade ago. Considering the functionality and complexity of the site it is a perfect candidate for an SPA.

I am contemplating what technology to use to build it. I'm set on an ASP.NET Core back-end as I am a .NET developer at heart and I will be able to salvage plenty of C# business logic from the old site, so this just makes sense.

What I'm not set on is the front-end. I've had an absolute nightmare the last week trying to set up React or Vue and never managed to get either working. Between all the templates being outdated, each framework having so many major versions in such a short space of time, the npm headache, and every person out there giving completely different advice for the same objective, it's just a constant battle with semantics to even start a blank project. I don't mind the idea of React and I will get it working if that's my better option here, but first, Blazor.

Blazor has just very recently been announced that it is no longer in experimental stage and is officially supported to be released at some point after .NET Core 3. I've used it before and it seems very performant, so I would love to continue doing so, I'm just not sure it's worth the risk, and here are my concerns:

1. It is very new and therefore documentation, libraries, UI components, etc are limited

2. It is not javascript and so I imagine it won't be possible to just npm some funky jquery controls in whenever they are needed

3. It is still in preview and as such may be a little buggy or cause other issues down the line

Is it worth the risk to start a production workload in Blazor? Perhaps getting in ahead of the curve will mean the project will be a long time away from needing another upgrade. Or is it just too much of a risk to consider this, and should I stick with the current trends of JS framework SPAs?