Initial rendering works fine on the server, but returns `<noscript>` in browser. about redux-async-connect HOT 4 OPEN

FYI, I also had an empty <noscript> markup in the server render, until I downgraded to 1.0.0-rc2

btw thank for the workaround ;)

from redux-async-connect.

I ran into this a few weeks ago getting going with redux-async on universal, but I forget what the solution was exactly. It was not an issue with redux-async. I remember logging out to the node console window the rendertostring of and then googled for what it said. It was a unrelated stack overflow or github issue that at least gave a clue on how to proceed.

from redux-async-connect.

I encountered the same issue on the server using the latest version of redux-async-connect (1.0.0-rc4), downgrading to 1.0.0-rc2 solved this discrepancy for me. Later I did encounter <noscript> being rendered on the client on one occasion - but in a completely different setup, so I'm afraid I can't provide any further pointers there.

One thing I do notice from the snippet is that you're not injecting your server data into createStore.

from redux-async-connect.

Yeah, I used to inject the data in the onEnter callbacks, but then I found that it isn't necessary. Initially, I also had a noscript issue on server, because I didn't use loadOnServer. Now it's good on server, but I still have noscript on client.

I'm using version "0.1.13", though. Maybe I should give "1.0.0-rc2" a try.

from redux-async-connect.