The problem of incomplete source code returned by SAP Spartacus server rendering and what is the solution

It is believed that many inexperienced people are at a loss about the problem of incomplete source code returned by SAP Spartacus server-side rendering and what is the solution. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

As shown in the following figure:

After I enable SSR locally, the server returns the rendered source code, and each cx-page-layout tag is empty:

But on the server used for SSR testing, the complete source code is returned:

Reason:

In addition, your backend may have an invalid certificate, which will cause angular SSR render to pass (so you will see regular non-CMS angular components rendered), but you will not see the CMS component of Spartacus rendered. To solve this problem in development, you can first install the "cross env" package, and then run "cross env NODE\ u TLS\ u REJECT\ u UNAUTHORIZED=0 NODE dist/storefrontapp server/main.js". After all this, you should be able to see a more reasonable response.

Solution:

Cross-env NODE_TLS_REJECT_UNAUTHORIZED=0 node dist/storefrontapp-server/main.js

After reading the above, have you mastered the problem of incomplete source code returned by SAP Spartacus server-side rendering and what the solution is? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!