geotic VS serialize-javascript

If you're using javascript I can't recommend geotic highly enough. I've used it on a bunch of games myself and have always had a pretty good experience. It's not a pure ECS architecture as it encourages logic in your components and events but that's mostly because it's based on talks given by the devs from ADOM and COQ - both of which seem to use ECS-like architecture. The repo has some nice example projects worth a look.

​ and this is my config for the plugin: { resolve:gatsby-plugin-react-redux-persist, options: { // [required] - path to your createStore module pathToCreateStoreModule: './src/store', // [optional] - options passed toserialize-javascript // info: https://github.com/yahoo/serialize-javascript#options // will be merged with these defaults: serialize: { space: 0, // ifisJSONis set tofalse,evalis used to deserialize redux state, // otherwiseJSON.parseis used isJSON: true, unsafe: false, ignoreFunction: true, }, // [optional] - if true will clean up after itself on the client, default: cleanupOnClient: true, // [optional] - name of key onwindowwhere serialized state will be stored, default: windowKey: '__PRELOADED_STATE__', }, },

We pass the entire state to the client-side via a script tag in the html document by using the serialize() function in the serialize-javascript package. (This javascript parser allows us to parse more object types like a Date so I would recommend to use that package instead of the JSON.stringify() function.) On the client-side we can now read the window.initialState object and parse it to the Redux store.