I'm just making this up in my head, because I'm pulling together random bits and pieces I've been reading all over, but with http2 isn't possible to do something clever with say splitting up the code so your initial paint is done with a smaller JS bundle and then it progressively loads the rest of your JS payload? It just seems this is something doable from all the bits and pieces I've read around the web. I just don't know if it's something that could be tied together and for a React scenario.
Yes, of course! :) There are techniques like tree shaking etc. which you can achieve through webpack, to reduce your client side payload, I am by no means an expert and 'know-it-all', that's why I wrote that people should probably first try to optimize their client side application as much as they can before attempting to go in to the dark side of server side rendering :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm just making this up in my head, because I'm pulling together random bits and pieces I've been reading all over, but with http2 isn't possible to do something clever with say splitting up the code so your initial paint is done with a smaller JS bundle and then it progressively loads the rest of your JS payload? It just seems this is something doable from all the bits and pieces I've read around the web. I just don't know if it's something that could be tied together and for a React scenario.
Yes, of course! :) There are techniques like tree shaking etc. which you can achieve through webpack, to reduce your client side payload, I am by no means an expert and 'know-it-all', that's why I wrote that people should probably first try to optimize their client side application as much as they can before attempting to go in to the dark side of server side rendering :)