Moving from isomorphic to website causes render service error
See original GitHub issueI am upgrading a site currently running the react-isomorphic-render
package to react-website
. After changing all the reducers to the new react-website
style (among other adjustments) I am now getting this not so helpful error in the console:
Render service is listening at port 3002
(node:25020) Warning: a promise was rejected with a non-error: [object Object]
(node:25020) Warning: a promise was rejected with a non-error: [object Object]
(node:25020) Warning: a promise was rejected with a non-error: [object Object]
(node:25020) Warning: a promise was rejected with a non-error: [object Object]
(node:25020) Warning: a promise was rejected with a non-error: [object Object]
[react-website] Rendering service error
Even more difficult is that web site itself simply appears as the word Error
with nothing in the console.
One possible problem I see is that preload was a reducer function with the old package. Should that reducer just be eliminated now?
Alternately, since this appears to be a promise problem, could this have anything to do with the site using bluebird
for promises?
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Error with routing in isomorphic server-side react project
It's OK, I figure it out. It was necessary to place the BrowswrRouter container in index.js, not in App.jsx. Here is corrected index.js:...
Read more >Isomorphic Rendering vs. Dynamic Rendering for JavaScript
Isomorphic JavaScript means that the application uses a similar rendering engine on the server and the client. This rendering method makes ...
Read more >Error handling in isomorphic node.js application
Step 1: Rendering. First step is to prevent initial rendering from breaking. It is the place in a code where method render() is...
Read more >The best of both worlds: SSR with isomorphic JavaScript
We're going to deploy a universal server-rendered React application created with create-react-app on Amazon Web Services (AWS). You don't need ...
Read more >An Overview of Server Side and Isomorphic Async Rendering
For an individual statement to qualify as Isomorphic, it has to be able to execute without error in both client and server JavaScript ......
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
I guess it wasn’t but no guarantees. There has been a lot of previous versions.
asyncSettings
are no longer required. I’d suggest removing them from code.