Serge van den Oever's weblog

Render Sitecore 9.1 JSS site using separate node server

February 07, 2019 • ☕️ 2 min read
If you like my writing
Buy me a coffee when you like my writing!

In a previous post I described how to use TypeScript in building JSS components. In this post I use the results of this connected hello-jss-typescript JSS app to build a custom Node express web server that consumes the layout service to render pages. This process is described by Sitecore in the documentation Headless SSR via sitecore-jss-proxy. I took the sample node-headless-ssr-proxy and worked from there.

I placed the code in a folder hello-jss-typescript-node next to the folder hello-jss-typescript as described in my post Developing React components in Typescript with Sitecore JSS 9.1.

The example provides an Express web server that I modified slightly for easy experimentation. It is great that all configuration is done through environment variables, but for development it is easier to use another approach. I added dotenv using npm install dotenv and added at the top of index.js the code:

if (process.env.NODE_ENV !== 'production') {

This enables us to add a file .env in the root to manage the required environment variables:


I also modified the index.js file slightly to work together with the hello-jss-typescript project:

if (process.env.NODE_ENV !== 'production') {

const express = require('express');
const compression = require('compression');
const scProxy = require('@sitecore-jss/sitecore-jss-proxy').default;
const config = require('./config');

const server = express();
const port = process.env.PORT || 3000;

// enable gzip compression for appropriate file types

// turn off x-powered-by http header
server.settings['x-powered-by'] = false;

// Serve static app assets from local /dist folder
  express.static('../hello-jss-typescript/build', {
    fallthrough: false, // force 404 for unknown assets under /disthello-jss-typescript/

// For any other requests, we render app routes server-side and return them
server.use('*', scProxy(config.serverBundle.renderView, config, config.serverBundle.parseRouteUrl));

server.listen(port, () => {
  console.log(`server listening on port ${port}!`);

Execute npm start and voila, the site is running on http://localhost:3000, completely separate from the Sitecore server.

Note that the .vscode folder contains a launch.json configured to debug the Node code in Visual Studio Code.

The complete example can be found at

Discuss on TwitterEdit on GitHub

Serge van den Oever's weblog

Serge van den Oever

Personal blog by Serge van den Oever - als je maar lol hebt...
Twitter: @svdoever
LinkedIn: Serge van den Oever - articles on LinkedIn

Technology Consultant @ Macaw
Competence Team Lead Custom Application Development @ Macaw
2022 Technology Sitecore Most Valuable Professional
2021 Technology Sitecore Most Valuable Professional

If you like my writing
Buy me a coffee when you like my writing!