Server Side Rendering not working
See original GitHub issueDo you want to request a feature or report a bug? Feature, unless SSR is supposed to be working
What is the current behavior? When trying to render TinyMCE on the server side in an application using dotnet core and angular I get the following exception:
Exception: Call to Node module failed with error: Prerendering failed because of error: ReferenceError: navigator is not defined
I don’t know if you have any plans to make TinyMCE to work with SSR but I open this just in case.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Server-side rendering not working on production Next.js
getServerSideProps only works in page components. Does this answer your question: NEXTJS: getServerSideProps not working into components?
Read more >Server-side rendering not working on production in Next.js ...
When using server-side rendering with next@12.1.6, the context doesn't get passed down to the children component.
Read more >Challenges in server side rendering React apps (SSR)
Data Hydration is a typical problem we encounter with server side rendering. The server has pre-fetched data. However, when we call ReactDOM.
Read more >Server-side rendering (SSR) with Angular Universal
The following Node.js Express code routes all remaining requests to /dist , and returns a 404 - NOT FOUND error if the file...
Read more >Data Fetching: getServerSideProps - Next.js
Pages using getServerSideProps will be server side rendered at request time and only ... If an error is thrown inside getServerSideProps , it...
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
Not something we support or have anything to do with.
Yes, TinyMCE was not built to function this way, the DOM is very much core to how TinyMCE operates.
This issue was closed over a year ago.