Automatic search and search results are not added into consideration for the SSR functionality, this means they do not SSR.
With the beforeSSRRender method this should be achievable as we can now capture props and state on the fly, however caution must be advised with the search state that is loaded from the navigation key, specially after this state must be loaded from the constructor and might not match the server state vs client state; this used to cause issues in the past and was moved to componentDidMount due to the search state loaded from navigation disrupting SSR.
Resources loaded via the HTMLResource loader should also be added into this list of SSR resource, this one should be rather easy.
This should drastically improve page responsiveness and SEO where these items appear, granted, they are not common use for this.
Automatic search and search results are not added into consideration for the SSR functionality, this means they do not SSR.
With the beforeSSRRender method this should be achievable as we can now capture props and state on the fly, however caution must be advised with the search state that is loaded from the navigation key, specially after this state must be loaded from the constructor and might not match the server state vs client state; this used to cause issues in the past and was moved to componentDidMount due to the search state loaded from navigation disrupting SSR.
Resources loaded via the HTMLResource loader should also be added into this list of SSR resource, this one should be rather easy.
This should drastically improve page responsiveness and SEO where these items appear, granted, they are not common use for this.