Some folks have attempted it, but not completed vite support.
This is nothing new in angular land. There are multiple third party libraries and framework which support react, vue, svelte and even solid, but not angular.
We did. But people without real problems to solve will continue reinventing the wheel, while we silently churn away on actual products with stable tooling.
Microframeworks are slightly better, especially if they support no-build setups since then a "build step" for prod is only bundling and minification.
I've worked on projects with hundreds of thousands of LOC compiling with Webpack. Build time has literally never been a concern for me. The entire point of tooling like Webpack is that it's written in JS because dealing with interop between native binaries is an absolute nightmare. It's a feature, not a bug. The same reason we moved to JS based SASS/PostCSS compilers.
So it sounds like Webpack was never really mature, or too late in getting ported to Go before Vite took over?
Wait what, again? I thought we all silently agreed to use the mature/legacy frameworks React and Angular until the proper WASM arrives so that we could burn all of JS/CSS/HTML...