SSR-ready bundle for the RDMD engine.

[rafegoldberg]

🧰 Changes

The Issue

We introduced some stop-gap SSR improvements yesterday that caused breakage on a small portion of pages using certain HTML entity characters. The issue stemmed from a sub-dependency of Unified which was referencing the browser's document global even when it was running on the server side.

The Fix

This PR adds a secondary SSR-specific webpack config with a target of "node", which builds a new dist/main.ssr.js bundle (per this suggestion):

api-explorer/packages/markdown/webpack.config.js

Lines 83 to 90 in 022ceec

	const serverConfig = merge(browserConfig, {
	target: 'node',
	output: {
	filename: '[name].node.js',
	},
	});
	module.exports = [browserConfig, serverConfig];

If we pull in this new SSR bundle, we can safely use the RDMD engine to server-side render our docs without worry as to this class of reference errors around undefined browser globals!

🚧 To Do

• Use the more conventional .node.js extension for the server-side bundle.
• Add/update the main and browser package fields.

🧪 Testing

Since we rolled back the SSR work last night we can't actually see this breakage in production, but you can see that the previously broken pages are now working in this PR app.

• ServiceNow
• Advanced ServiceNow Configuration
• ServiceNow FAQ
• ServiceNow Troubleshooting Guide

To verify that the SSR is working for yourself, try reloading with Javascript disabled. You should see the doc's content when using this staging app, but not on production.