That’s a strawman. I don’t need 1000s of lines of JS to swap a UI. I can do it in 1 line with Web Components: oldElement.replaceWith(newElement). And those modules can be lazy loaded like anything else.

This is just DX in name of UX, which is almost never a good idea.

And maybe you’re fine with throwing a server computation for every single UI change, but I’m not made of money and I much rather have stuff on a CDN.

C’mon, what’s not to like about bonding every UI action against a remote server? What’s a few milliseconds anyway? I’m sure it works fine over cellular networks. I mean, it works great on my dev machine! /s

PascalCase default exports for Classes

camelCase named exports for functions

ALL_CAPS named exports for constants

Outside of PWA shortcomings, I believe there’s a way to have a .NET application run a WebView with Edge (Chromium). I believe Windows 11 has both pre-installed now.

I don’t even want to run NodeJS anymore. I would run all my server apps on headless Chromium if I could.