Node.js rendering engine
The Node.js rendering engine uses a
node.js instance must run on the Content Delivery (CD) server.
The Node.js rendering engine is not usable with JSS for Next.js or ASP.NET Rendering SDK applications.
NodeServices. Node.js returns a response containing the HTML string.
The page-level items that correspond to the route are expected to have conventional presentation details set on them:
Using a layout based on the
JSS App triggers rendering by Headless Services using the rendering engine configured for the JSS application. The layouts, in this case, serve only as indicators and point at empty Razor views. The
WelcomeRendering is a real Sitecore rendering item of the type
In their server bundle, the JSS applications export and invoke a
renderView function that consumes the response to produce the static rendering of the application. Data passed into this function is double encoded to preserve JSON formatting and must be parsed with
JSON.parse() before use.
Pros and cons of the Node.js rendering engine
It is simple to set up. Install
node.json the Sitecore server and add the node executable to the
You do not have to manage
You have limited customization options of
node.jsstartup, profiling, debugging.
You have limited control over pooling/clustering.
You need to install
node.json Sitecore servers.
You must deploy JSS app artifacts to the Sitecore server.
Not usable with Next.js or ASP.NET Core