2 ms·
...which are a whole damn thing. Don't get me wrong I'm glad the React team is tackling the problem but it's telling that the answer requires an entire server
by afavour 4y ago
...which are a whole damn thing.
Don't get me wrong I'm glad the React team is tackling the problem but it's telling that the answer requires an entire server side solution when other JS frameworks are able to solve this in the client or at build time. And just looking at those docs screams "patching over a fundamental issue" to me.