"ReferenceError: document is not defined" at End of Project Build

[gchallen]

Description

I just started seeing this error at the end of gastby build (on a project that has previously built successfully many times):

success onPostBuild - 0.011s
info Done building in 202.735335441 sec

/Users/challen/cs125/www/sites/cs125/public/render-page.js:76707
    return document.createElementNS ?
    ^

ReferenceError: document is not defined
    at Object.exports.createElement (/Users/challen/cs125/www/sites/cs125/public/render-page.js:76707:5)
    at Text.$renderToken (/Users/challen/cs125/www/sites/cs125/public/render-page.js:92653:33)
    at Text.$renderSimpleLine (/Users/challen/cs125/www/sites/cs125/public/render-page.js:92758:33)
    at Text.$renderLine (/Users/challen/cs125/www/sites/cs125/public/render-page.js:92799:22)
    at Text.$renderLinesFragment (/Users/challen/cs125/www/sites/cs125/public/render-page.js:92552:18)
    at Text.update (/Users/challen/cs125/www/sites/cs125/public/render-page.js:92578:25)
    at VirtualRenderer.$renderChanges (/Users/challen/cs125/www/sites/cs125/public/render-page.js:94634:29)
    at Timeout.RenderLoop._flush [as _onTimeout] (/Users/challen/cs125/www/sites/cs125/public/render-page.js:93276:19)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)

Note that this doesn't seem to affect the resulting build, but it's somewhat disturbing.

Steps to reproduce

Run gatsby build.

Expected result

The build should complete without warning.

Actual result

The error above is thrown.

Environment

  System:
    OS: macOS 11.2.1
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
    Shell: 5.0.17 - /opt/local/bin/bash
  Binaries:
    Node: 12.18.3 - ~/.asdf/installs/nodejs/12.18.3/bin/node
    npm: 6.14.6 - ~/.asdf/installs/nodejs/12.18.3/bin/npm
  Languages:
    Python: 3.8.3 - /Users/challen/.asdf/shims/python
  Browsers:
    Chrome: 88.0.4324.182
    Firefox: 84.0.2
    Safari: 14.0.3
  npmPackages:
    gatsby: ^2.32.4 => 2.32.4
    gatsby-alias-imports: ^1.0.6 => 1.0.6
    gatsby-image: ^2.11.0 => 2.11.0
    gatsby-link: ^2.11.0 => 2.11.0
    gatsby-plugin-anchor-links: ^1.2.1 => 1.2.1
    gatsby-plugin-google-fonts: ^1.0.1 => 1.0.1
    gatsby-plugin-manifest: ^2.12.0 => 2.12.0
    gatsby-plugin-material-ui: ^2.1.10 => 2.1.10
    gatsby-plugin-mdx: ^1.10.0 => 1.10.0
    gatsby-plugin-pnpm: ^1.2.5 => 1.2.5
    gatsby-plugin-react-helmet: ^3.10.0 => 3.10.0
    gatsby-plugin-sass: 3.2.0 => 3.2.0
    gatsby-plugin-sharp: ^2.14.1 => 2.14.1
    gatsby-plugin-typescript: ^2.12.0 => 2.12.0
    gatsby-remark-graphviz: ^1.10.0 => 1.10.0
    gatsby-source-filesystem: ^2.11.0 => 2.11.0
    gatsby-transformer-sharp: ^2.12.0 => 2.12.0

[KyleAMathews]

It's possible you installed a new version of a dependency which added this. You can look at the stacktrace to see where it's coming from e.g. what is Text.$renderToken.

[gchallen]

No clue. Is there any way to get at the contents of render-page.js? It looks like it's removed from the public folder after the build completes.

[gchallen]

It's also weird in that it doesn't happen consistently, even on the same code. I'd say it occurs about 50% of the time. So it seems like some kind of race.