New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when used with Gatsby: error "window" is not available during server side rendering. #73
Comments
Sounds like this is just a general issue with SSR compatibility with libraries that use browser-only APIs. Have you looked at gatsbyjs/gatsby#309? It's not specific to this library, so I'm closing for now. |
@nickforddesign I have looked at that 馃槃 and while the general error isn't specific to this library, the issue is that freezeframe.js accesses the Generally, the solution for getting code that tries to do that is to have it either:
More recently, Would you be open to any of these changes, and if so, could you please reopen this issue? There is behavior done in this library that makes it difficult to use in frameworks such as Gatsby. |
Thanks for clarifying, I will look at this |
Thank you very much! I'd be happy to help / send a PR / etc., if it's useful at all. |
hi everybody, I'm getting the same error when using next.js. I tried defining |
Did anyone manage to find a way around this for gatsby projects. |
in general I'd recommend that SSR be skipped for this components, even JSDOM doesn't fully implement the canvas APIs required. So, whatever SRR framework you are using, let it skip freezeframe components. |
The project isn't open source 馃槥 but here's a relevant snippet from a build:
gatsby-log.txt
The text was updated successfully, but these errors were encountered: