Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error when used with Gatsby: error "window" is not available during server side rendering.

See original GitHub issue

The project isn’t open source 😞 but here’s a relevant snippet from a build:

5:22:47 PM: error "window" is not available during server side rendering.
5:22:47 PM: 
5:22:47 PM: > 1 | !function(t,n){"object"==typeof exports&&"object"==typeof module?module.exports=n():"function"==typeof define&&define.amd?define([],n):"object"==typeof exports?exports.Freezeframe=n():t.Freezeframe=n()}(window,(function(){return function(t){var n={};function e(r){if(n[r])return n[r].exports;var i=n[r]={i:r,l:!1,exports:{}};return
...

Visually, the top of the request gatsby-log.txt

Issue Analytics

State:
Created 3 years ago
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

jonrriveracommented, Dec 21, 2020

https://www.npmjs.com/package/react-freezeframe !!

1reaction

jonrriveracommented, Dec 21, 2020

hi everybody, I’m getting the same error when using next.js. I tried defining if (typeof window !== "undefined") { new Freezeframe(); } which removed the ‘window not defined error’, but now the project is not compiling. Please let me know if you need any further clarification. thank you!