fix(gatsby): pull out a few bug fixes from #28149

gatsbyjs · Nov 19, 2020 · a1d4468 · a1d4468
1 parent 413888b
commit a1d4468
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/packages/gatsby/src/services/initialize.ts b/packages/gatsby/src/services/initialize.ts
@@ -71,7 +71,7 @@ This will help the dev environment more closely mimic builds so you'll catch bui
 
 Try out develop SSR *today* by running your site with it enabled:
 
-GATSBY_EXPERIMENT_DEV_SSR=true gatsby develop
+GATSBY_EXPERIMENTAL_DEV_SSR=true gatsby develop
 
 Please let us know how it goes good, bad, or otherwise at gatsby.dev/dev-ssr-feedback
       `,

diff --git a/packages/gatsby/src/utils/dev-ssr/render-dev-html.ts b/packages/gatsby/src/utils/dev-ssr/render-dev-html.ts
@@ -3,6 +3,7 @@ import _ from "lodash"
 
 import { startListener } from "../../bootstrap/requires-writer"
 import { findPageByPath } from "../find-page-by-path"
+import { getPageData as getPageDataExperimental } from "../get-page-data"
 
 const startWorker = (): any => {
   const newWorker = new JestWorker(require.resolve(`./render-dev-html-child`), {
@@ -63,6 +64,9 @@ export const renderDevHTML = ({
       isClientOnlyPage = true
     }
 
+    // Ensure the query has been run and written out.
+    await getPageDataExperimental(pageObj.path)
+
     try {
       const htmlString = await worker.renderHTML({
         path,