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.
Breaks with server-side rendering
See original GitHub issueWe have a react application with server-side rendering. Filestack-js attempts to extend the browser-only File prototype at compile-time.
Please only do this in the init() method, so that we can use this lib in our application.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
[2.0.0] Server-side rendering breaks · Issue #1890 - GitHub
Description Reanimated v2 stable breaks server side rendering, because it uses window.performance in the constructor of JSReanimated.
Read more >Stop Client Side and Server Side Rendering. Do This Instead.
Server -side rendering involves two renders. First, the server executes the data fetches and creates a fully rendered HTML page to send to...
Read more >The Challenges and Pitfalls of Server Side Rendering
Server - Side Rendering (SSR) has become a go-to method for improving the load time of dynamic websites. Rendering content on the server...
Read more >The future of rendering in React - Prateek Surana
The way that server-side rendering works in React right now is: ... new features with Suspense that allow you to break down your...
Read more >Server-side rendering broken after upgrading to MUI 5 (with ...
Issue for me was React 18. Reverted back to React 17 in package.json \ "dependencies": { "react": "17.0.2", "react-dom": "17.0.2".
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@zimme Yeah looks like I missed one more spot where we assume a browser environment. I will hopefully have this fixed in 0.7.0.
Thanks for the feedback! I will look into getting this resolved soon.