The two examples have diverged slightly since then and there a couple difference between the two:
- This example utilizes the next-apollo package which is ideal if you prefer to use Apollo explicitly on a page-by-page basis, as it requires you to wrap every page where you use Apollo in a HOC. If you prefer to use Apollo implicitly on every page, I recommend using the other example.
- This example features my preferred CSS-in-JS solution, Emotion, whereas the other example features styled-jsx (for those who prefer a more traditional CSS syntax).
How to use
Install it and run
npm install npm run dev
The idea behind the example
Apollo is a GraphQL client that allows you to easily query the exact data you need from a GraphQL server. In addition to fetching and mutating data, Apollo analyzes your queries and their results to construct a client-side cache of your data, which is kept up to date as further queries and mutations are run, fetching more results from the server.
In this simple example, we integrate Apollo seamlessly with Next by wrapping our pages inside a higher-order component (HOC). Using the HOC pattern we're able to pass down a central store of query result data created by Apollo into our React component hierarchy defined inside each page of our Next application.
On initial page load, while on the server and inside
getInitialProps, we invoke the Apollo method,
getDataFromTree. This method returns a promise; at the point in which the promise resolves, our Apollo Client store is completely initialized.