4 ms·
Have we solved the issue of server-side rendering + code splitting? I see both in features, but last time we attempted this, we had to give up one of those feat
by azmenak 9y ago
Have we solved the issue of server-side rendering + code splitting? I see both in features, but last time we attempted this, we had to give up one of those features.
- tirthbodawala 9y agoYes we have.. with "pages" we can do that now. I can explain more if needed :)
- fiatjaf 9y agoWhat is code-splitting? Is it asynchronous loading of components? If you're interested in a React-based static site generator that does that: https://github.com/fiatjaf/sitio https://github.com/fiatjaf/sitio
- yashthakur 9y agoIt means load only the code for the page/route that you are visiting and not the code of entire site. Suppose you visit only example.com/about-us page then why should the server load example.com, example.com/faq, example.com/blog code together with it? I hope you got the point of code-splitting. :)
- fiatjaf 9y agoA new name for a very old concept. People keep inventing these things...
- aljones 9y agoNext.js does it.