Hey @JClackett,

Thanks a lot for sharing this project, I learned a lot from it and it was a great starting point for my graphql typeorm boilerplate.
I like your approach of querying GraphQL API from components, very clean. Unfortunatly, we can't use hooks like useQuery / useMutation in getServerSideProps, and sometimes I'd like to query my GraphQL API directly in getServerSideProps (for example to handle redirect server side).

I followed recent discussions about calling GraphQL API in getServerSideProps, then handle client side querying (for pagination for instance) and stumbled upon your updated version (with initial cache update) of the next js with-apollo example so I guess you're stil using apollo client in your new projects.

I saw there was other way of doing that with graphql-request + swr / react-query or urql which are lighter but does not seem to handle the cache part as well as apollo.

I was wondering if you also sometimes need to query the GraphQL API from getServerSideProps and if that's the case, if you could share a gist of what approach you picked?

I'd also be interested to know if you made the switch to next js api routes vs custom server on your new projects as there seems to be some problems with HMR + typeorm?

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid regExp for packageRules[0].packagePatterns: eslint, Invalid regExp for packageRules[1].packagePatterns: @types/``