SSR/Browser API questions

[tonyhallett]

There are differences in the arguments passed to
https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/cache-dir/static-entry.js
https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/cache-dir/develop-static-entry.js
https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/cache-dir/ssr-develop-static-entry.js

static-entry.js onPreRenderHTML has an additional field pathPrefix

Should the pathPrefix be added to the other two js files and then be documented ?

replaceRenderer is not available in develop-static-entry but in the other two the pathPrefix field is present. Should this be documented ?

There are additional fields for static-entry for onRenderBody. They are not documented. Should they be ?

    apiRunner(`onRenderBody`, {
      setHeadComponents,
      setHtmlAttributes,
      setBodyAttributes,
      setPreBodyComponents,
      setPostBodyComponents,
      setBodyProps,
      pathname: pagePath,
      
      //additional
      loadPageDataSync,
      bodyHtml,
      scripts,
      styles,
      pathPrefix: __PATH_PREFIX__,
    })

--
wrapRootElement is different for
SSR

    const bodyComponent = (
      <StaticQueryContext.Provider value={staticQueryContext}>
        {apiRunner(
          `wrapRootElement`,
          { element: routerElement, pathname: pagePath },
          routerElement,
          ({ result }) => {
            return { element: result, pathname: pagePath }
          }
        ).pop()}
      </StaticQueryContext.Provider>
    )

and Browser

 const { pagePath, location: browserLoc } = window

    const SiteRoot = apiRunner(
      `wrapRootElement`,
      { element: <LocationHandler /> },
      <LocationHandler />,
      ({ result }) => {
        return { element: result }
      }
    ).pop()

should the pathname (pagePath) be available to browser api ?