Storing “global” object outside of Redux store in React/Redux app

[stevenmusumeche]

I apologize in advance if this is an inappropriate venue for this type of question.

I am building a React/Redux app that needs a globally available object (a websocket lib instance). I originally tried to store this in the Redux state tree, however, the instance is not immutable and it caused lots of problems with hot reloading during development (tons of circular reference errors that don't exist when running from compiled code).

My question is how to store/create this instance so that it is available to my Redux code and React components? I could create it at the very top of the component tree and pass it down the tree as a prop, but that feels very "dirty" after doing everything with react-redux connect.

Is there a better way to do this?

[markerikson]

Yeah, usage questions should really be asked over on Stack Overflow.

Middleware is a good place for persistent connection-type objects. There's a bunch of existing middlewares that wrap around websockets, Firebase, and various other connection types, listed over at https://github.com/markerikson/redux-ecosystem-links/blob/master/middleware.md#sockets-and-adapters. You might be able to use one of those as-is, or at least get inspiration from some of them.

[emmby]

The stackoverflow link for posterity: http://stackoverflow.com/questions/37221872/storing-global-object-outside-of-redux-store-in-react-redux-app