Error: Future resolved more than once about react-isomorphic-video-game-search HOT 7 CLOSED

Hi Pavel,

The error occurs when the app attempts to bootstrap itself more than once. My apologies, as there is no need for alarm. This should fail silently, but I did not remove the debug logging before I committed.

from react-isomorphic-video-game-search.

I mean, new event listener has been added on every new request when you call gameStore.listen(...).
It can be possible memory leak and/or performance degradation.
I've tested (with ab -c 5 -t 10 http://localhost:3000/) on my own application with similar code and got performance degradation (from 100rps to 20rps).

from react-isomorphic-video-game-search.

I'm getting the same error and if it affects the performance I would like to know how to fix

from react-isomorphic-video-game-search.

This is an unfortunate byproduct of react-async, which requires node-fibers, when initializing state for the same component asynchronously multiple times.

I have been researching better ways of solving the problems outlined in this project, including isomorphic flux and server-side canonical URLs. As a result, I will likely update this project with a new implementation powered by alt and react-router.

from react-isomorphic-video-game-search.

is there any news about the updated version which powered by alt and react-router?

from react-isomorphic-video-game-search.

Between the rapidly evolving React/Flux landscape and other competing interests, I have decided not to make this a priority.

That said, I do hope to revisit this project, which is simply an example demo for some planned projects, in a month or so.

from react-isomorphic-video-game-search.

@chadpaulson I can wait for a month, this repo is the most minimal isomorphic one I seen.

from react-isomorphic-video-game-search.