Task Queue

12/31/2021

Working on universal server page rendering in combination with migrating to open search.

Universal server is not waiting long enough to allow page rendering. Need to identify the cause of this. The page is being handed off to the browser in incomplete state without content. This doesn't really impact experience because Angular will than navigate properly in the browser but that content is not physically part of the dom. The primary goal of universal rendering is to make the page content physically part of the dom.

Someone in a thread made an interesting point as to what could be the cause of this.

Yeah I did understand the problem, but this is often caused because of a server side error during SSR (not talking about the API, but the nodejs process doing SSR). If everything is fine server side, I'm not sure what could be causing the issue.

Thread Reference: https://stackoverflow.com/questions/52270397/angular-6-angular-universal-not-waiting-on-content-api-call