Angular's TransferState class enables server-side rendering (SSR) and pre-rendering (SSR) Angular applications to efficiently render in the browser using data fetched from the server.

I created a storefront with Schematics based on version 3.4.5 (which a customer is using) and ran it in SSR mode.

I visit http://localhost:4000/ in my browser.

From Chrome Dev Tools I know that the source code of the home page is successfully generated by the SSR server.

However, even in SSR mode, I found that the /cms/pages OCC API is still triggered from the client.

In the log of the SSR server, I did not find the CSR fallback:

However, on the client side, I still found these OCC API calls:

Even if I use code like this:

ConfigModule.withConfig({ state: { ssrTransfer: { keys: { products: true, cms: true } } }});

Only make sure that the client is not sending product related API calls.

Answers

• For Product - I guess the status has moved from SSR to CSR.
• For cms - I guess we make the call whether we are in the ngrx store or not.What we are discussing may be improved in the future

By default, Spartacus reloads CMS page data on every route change, regardless of whether it is already maintained in ngrx state.However, customers can configure routing.loadStrategy differently via Spartacus: RouteLoadStrategy.ONCE
It is used in the CmsPageGuard.shouldReload method.