-
Notifications
You must be signed in to change notification settings - Fork 640
getting "listen is undefined" error when working with redux-router's new history object #173
Comments
apologies, too tired to make much sense. I got it working vaguely by explicitly depending on history and creating a new browserHistory to seed into SyncReduxAndRouter. But it leaves hashes all over the url :( |
Without a reproducible example we have no way of helping you. Quite a few of us use this already, so without code it's difficult to say what the problem is with your setup. I'll close this for now, but let's re-open this when you add an example we can look at :) |
my sincere apologies. way too tired to be thinking straight. I had the wrong react-router version, which didn't have a history, and therefore didn't have listen. So easy to resolve once I'd slept ;) thanks for the awesome work, keep it up :) |
I am actually having this problem with [email protected]. Issue is that browserHistory returns undefined on serverside: So, I assume redux-simple-router should either guard against that, or should I just not load the middleware when server side? |
You should pass it a memory history that you create yourself. We also export a |
it doesn't appear to have a listen method
The text was updated successfully, but these errors were encountered: