As the title states I have a Gatby.js site. I have my own graphql API and use gatsby-source-graphql to access it.

I really like the idea of how gatsby-image works however the examples are quite limited to wordpress and files that are stored locally.

inside gatsby-node.js i export createPages. The data is requested from my graphql API and the results contains the slug which i use to create the page. it also contains the media urls which i could use inside createRemoteFileNode, however I have no idea how to connect it back to the entity that was returned if that makes sense.

I was planning on using gatsby.js and store all the files, including the code on s3 with cloudfront on top of it. I mean i could still copy the files over to s3 manually and somehow access the data based on the data that is in the database right now

Most projects I'm aware of are writing ES6 modules (import, etc), but still bundling/compiling them down to ES5 using whatever build system their team/framework uses (webpack, gulp, etc).

I'm not aware of (m)any that are writing CommonJS or AMD modules directly, because that code will already be obsolete as soon as it's written, and pretty much every major tool/packaging system should understand ES6 module syntax by now.

One way is to use a state and lifecycle methods to handle this. So you can add event listener in componentDidMount in your stateful class based component and change state when the screen resizes and pass props to the stateless component. Don't forget to unsubscribe event listener in componentWillUnmount.

Which is more performant, redux or context? If I'm not mistaken redux uses context in the background.

Maybe having multiple separate contexts would be more performant than a single redux store, or a single context for that matter?

The reason I'm asking is that I've recently inherited project where the developer is using redux for managing UI state such as hover over a google map marker highlights something in a sidebar and vice versa.

However with too many markers there is significant lag in the hover state (ui wise). Now the components aren't that far apart so maybe just lifting the state into container component would be sufficient, however there would still be some prop drilling involved.