3 ms·
You don't necessarily need the whole server-side dance: https://jsfiddle.net/chrisvfritz/50wL7mdz/ https://jsfiddle.net/chrisvfritz/50wL7mdz/ I find developin
by founderling 7y ago
You don't necessarily need the whole server-side dance:
https://jsfiddle.net/chrisvfritz/50wL7mdz/ https://jsfiddle.net/chrisvfritz/50wL7mdz/
I find developing without a server side build process much more lightweight and enjoyable.
- muhammadusman 7y agoThanks for the suggestion. My example app is pretty contrived but I was mostly running into this issue when I had a multi-component app. An example is another repo I was working on: https://github.com/usmanity/prompt/tree/master/src https://github.com/usmanity/prompt/tree/master/src I guess, I should've prefaced my blog post with that :p
- fimdomeio 7y agoI'm currently batling with this and components inside components, not sure how to do it nor where to find info for it. if anyone as any guide would be very much appreciated.
- awinder 7y agoIn a lot of cases you really don't want a server at that layer of the stack anyways, when you could be serving your site from a CDN/"edge" that's built for low-latency to end users, cost-optimized for transfer and not having to play all of the games that scaling yet another layer brings. I'm willing to believe that some people really need server side rendering but it'd a hard sell to convince me that the majority of people chasing SSR really need it, or that they're better off for it.