d72d3c09ef
Prior to react-apollo 2.0 createNetworkInterface accepted the credentials option in {opt: {credentials: 'policy'}}. HttpLink accepts it as {credentials: 'policy'}.
|
||
|---|---|---|
| .. | ||
| components | ||
| lib | ||
| pages | ||
| package.json | ||
| README.md | ||
Apollo Example
Demo
https://next-with-apollo.now.sh
How to use
Download the example or clone the repo:
curl https://codeload.github.com/zeit/next.js/tar.gz/master | tar -xz --strip=2 next.js-master/examples/with-apollo
cd with-apollo
Install it and run:
npm install
npm run dev
Deploy it to the cloud with now (download):
now
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.
This example relies on graph.cool for its GraphQL backend.
Note: Apollo uses Redux internally; if you're interested in integrating the client with your existing Redux store check out the with-apollo-and-redux example.