pimterry/loglevel

WebpackError: ReferenceError: window is not defined

webjay opened this issue · 4 comments

webjay commented

When building with GatsbyJS I get this error:

"window" is not available during server side rendering.

WebpackError: ReferenceError: window is not defined

Here's what Gatsby has to say about it:
https://www.gatsbyjs.org/docs/debugging-html-builds/

I'd like to import:

import log from 'loglevel';
import remote from 'loglevel-plugin-remote';

but I need to do it like this:

const log = typeof window !== 'undefined' ? require('loglevel') : null;
const remote = typeof window !== 'undefined' ? require('loglevel-plugin-remote') : null;
pimterry commented

Which version of loglevel are you using? Does it say where exactly in the code this is failing?

Loglevel attempts to guard against exactly this by checking if window is available everywhere, and works fine in node without window, so there's something unusual happening to cause this.

webjay commented

Versions:

"loglevel": "1.6.8",
"loglevel-plugin-remote": "0.6.8",

Here's what I get:

yarn gatsby --verbose build
yarn run v1.22.4
$ /Users/jacob/Sites/cotrain/node_modules/.bin/gatsby --verbose build
verbose set gatsby_log_level: "verbose"
verbose set gatsby_executing_command: "build"
verbose loading local command from: /Users/jacob/Sites/cotrain/node_modules/gatsby/dist/commands/build.js
verbose running command: build
success open and validate gatsby-configs - 0.242s
success load plugins - 3.321s
success onPreInit - 0.104s
success delete html and css files from previous builds - 0.147s
info One or more of your plugins have changed since the last time you ran Gatsby. As
a precaution, we're deleting your site's cache to ensure there's no stale data.
success initialize cache - 0.229s
success copy gatsby files - 0.554s
success onPreBootstrap - 3.164s
success createSchemaCustomization - 0.130s
verbose Now have 43 nodes with 7 types: [SitePage:1, SitePlugin:37, Site:1, SiteBuildMetadata:1, Directory:1, File:1, ImageSharp:1]
success source and transform nodes - 0.336s
success building schema - 2.364s
verbose Now have 43 nodes with 7 types, and 1 SitePage nodes
success createPages - 0.013s
success createPagesStatefully - 0.691s
success updating schema - 0.234s
success onPreExtractQueries - 0.005s
success extract queries from components - 2.582s
success write out requires - 0.014s
success write out redirect data - 0.102s
success Build manifest and related icons - 1.760s
success onPostBootstrap - 1.783s
info bootstrap finished - 28.415s
success run static queries - 0.180s - 1/1 5.55/s
success Building production JavaScript and CSS bundles - 152.608s
success Rewriting compilation hashes - 0.040s
success run page queries - 0.150s - 6/6 39.90/s
failed Building static HTML for pages - 33.472s

 ERROR #95312 

"window" is not available during server side rendering.

See our docs page for more info on this error: https://gatsby.dev/debug-html





  WebpackError: ReferenceError: window is not defined
  
  - build-html.js:107 doBuildPages
    [cotrain]/[gatsby]/dist/commands/build-html.js:107:24
  
  - build-html.js:121 async buildHTML
    [cotrain]/[gatsby]/dist/commands/build-html.js:121:3
  
  - build.js:215 async build
    [cotrain]/[gatsby]/dist/commands/build.js:215:5
  

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
webjay commented

My bad, this is only happening for loglevel-plugin-remote.

pimterry commented

Ok! Glad to hear you've narrowed down the issue, do let me know if there's anything else I can do to help on the loglevel side.

  • 👍1