apollographql · Jul 19, 2017 · Jul 19, 2017 · Jul 20, 2017 · Jul 20, 2017 · Jul 20, 2017
diff --git a/.flowconfig b/.flowconfig
diff --git a/.github/ISSUE_REPLY_TEMPLATE.md b/.github/ISSUE_REPLY_TEMPLATE.md
diff --git a/.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/bug.md
@@ -1,30 +1,42 @@
+---
+name: 🐛 Reporting a Bug
+about: Open a new issue here if something isn't working as expected.
+---
+
 <!--
   Thanks for filing an issue on React Apollo!
 
   Please make sure that you include the following information to ensure that your issue is actionable.
 
   If you don't follow the template, your issue may end up being closed without anyone looking at it carefully, because it is not actionable for us without the information in this template.
 
-  If you're filing a feature request, you do not need to follow the outline below, but please include "feature idea" in the title and include a specific example in which that feature would be useful.
+  **PLEASE NOTE:** Feature requests and non-bug related discussions are no longer managed in this repo. Feature requests should be opened in https://github.com/apollographql/apollo-feature-requests.
 -->
 
 **Intended outcome:**
+
 <!--
 What you were trying to accomplish when the bug occurred, and as much code as possible related to the source of the problem.
 -->
 
 **Actual outcome:**
+
 <!--
 A description of what actually happened, including a screenshot or copy-paste of any related error messages, logs, or other output that might be related. Places to look for information include your browser console, server console, and network logs. Please avoid non-specific phrases like “didn’t work” or “broke”.
 -->
 
 **How to reproduce the issue:**
+
 <!--
-If possible, please create a reproduction using https://github.com/apollographql/react-apollo-error-template and link to it here. If you prefer an in-browser way to create reproduction, try https://codesandbox.io/s/7361K9q6w
+If possible, please create a reproduction using https://github.com/apollographql/react-apollo-error-template and link to it here. If you prefer an in-browser way to create reproduction, try: https://codesandbox.io/s/github/apollographql/react-apollo-error-template 
 
 Instructions for how the issue can be reproduced by a maintainer or contributor. Be as specific as possible, and only mention what is necessary to reproduce the bug. If possible, try to isolate the exact circumstances in which the bug occurs and avoid speculation over what the cause might be.
 -->
 
 **Version**
-- apollo-client@<version number>
-- react-apollo@<version number>
+
+<!--
+Run the following command in your project directory, and paste its (automatically copied to clipboard) results here:
+
+`npx envinfo@latest --preset apollo --clipboard`
+-->
diff --git a/.github/ISSUE_TEMPLATE/feature-request.md b/.github/ISSUE_TEMPLATE/feature-request.md
@@ -0,0 +1,8 @@
+---
+name: 🚀 Feature Request
+about: Feature requests are managed in the Apollo Feature Request repo (https://github.com/apollographql/apollo-feature-requests).
+---
+
+Thanks for your interest in helping make React Apollo better!
+
+Feature requests and non-bug related discussions are no longer managed in this repo. Feature requests should be opened in https://github.com/apollographql/apollo-feature-requests.
diff --git a/.github/ISSUE_TEMPLATE/question-discussion.md b/.github/ISSUE_TEMPLATE/question-discussion.md
@@ -0,0 +1,10 @@
+---
+name: 🤗 Question / Discussion
+about: Questions / discussions are best posted in Apollo's Spectrum community or StackOverflow.
+---
+
+Need help or want to talk all things React Apollo? Issues here are reserved for bugs, but one of the following resources should help:
+
+* Apollo Spectrum community: https://spectrum.chat/apollo
+* StackOverflow (`react-apollo` tag): https://stackoverflow.com/questions/tagged/react-apollo
+* Apollo Feature Request repo: https://github.com/apollographql/apollo-feature-requests
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -20,6 +20,7 @@
 
 ### Checklist:
 
-- [ ] If this PR is a new feature, please reference an issue where a consensus about the design was reached (not necessary for small changes)
-- [ ] Make sure all of the significant new logic is covered by tests
-- [ ] If this was a change that affects the external API used in GitHunt-React, update GitHunt-React and post a link to the PR in the discussion.
+* [ ] If this PR is a new feature, please reference an issue where a consensus about the design was reached (not necessary for small changes)
+* [ ] Make sure all of the significant new logic is covered by tests
+* [ ] If this was a change that affects the external API used in GitHunt-React, update GitHunt-React and post a link to the PR in the discussion.
+
diff --git a/.github/config.yml b/.github/config.yml
diff --git a/.github/no-response.yml b/.github/no-response.yml
diff --git a/.github/probot-snooze.yml b/.github/probot-snooze.yml
diff --git a/.github/stale.yml b/.github/stale.yml
diff --git a/.gitignore b/.gitignore
@@ -1,36 +1,10 @@
-# Logs
-logs
-*.log
-
-# Runtime data
-pids
-*.pid
-*.seed
-
-# Directory for instrumented libs generated by jscoverage/JSCover
-lib-cov
-
-# Coverage directory used by tools like istanbul
+.rpt2_cache
+meta
 coverage
-
-# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
-.grunt
-
-# node-waf configuration
-.lock-wscript
-
-# Compiled binary addons (http://nodejs.org/api/addons.html)
-build/Release
-
-# Dependency directory
-# https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git
 node_modules
-
-# don't commit compiled files
+build
+npm
 lib
-test-lib
-dist
-
-# don't track yarn lock but allow contributors to use it for local dev
 yarn.lock
-package-lock.json
+examples/**/package-lock.json
+junit.xml
diff --git a/.gitleaks.toml b/.gitleaks.toml
@@ -0,0 +1,8 @@
+
+[[ rules ]]
+    id = "high-entropy-base64"
+    [ rules.allowlist ]
+        commits = [
+            "f405cbae562870230d441062bf220a3988bc0294",
+
+        ]
diff --git a/.npmignore b/.npmignore
diff --git a/.travis.yml b/.travis.yml
diff --git a/.vscode/launch.json b/.vscode/launch.json
diff --git a/.vscode/launchReactNative.js b/.vscode/launchReactNative.js
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -1,25 +1,4 @@
-// Place your settings in this file to overwrite default and user settings.
 {
-  "editor.tabSize": 2,
-  "editor.rulers": [100],
-  "files.trimTrailingWhitespace": true,
-  "files.insertFinalNewline": true,
-  "files.exclude": {
-    "**/.git": true,
-    "**/.DS_Store": true,
-    "node_modules": false,
-    "test-lib": true,
-    "lib": false,
-    ".gitignore": true,
-    ".npmignore": true,
-    ".travis.*": false,
-    "appveyor.yml": true,
-    "LICENSE": true,
-    "typings.d.ts": false,
-    "tsconfig.json": false,
-    "tslint.json": true,
-    "coverage": true
-  }
-,
-"typescript.tsdk": "./node_modules/typescript/lib"
-}
+  "editor.formatOnSave": true,
+  "prettier.singleQuote": true
+}
diff --git a/.vscode/spell.json b/.vscode/spell.json
diff --git a/.vscode/typings/react-native/react-native.d.ts b/.vscode/typings/react-native/react-native.d.ts
diff --git a/.vscode/typings/react/react-addons-create-fragment.d.ts b/.vscode/typings/react/react-addons-create-fragment.d.ts
diff --git a/.vscode/typings/react/react-addons-css-transition-group.d.ts b/.vscode/typings/react/react-addons-css-transition-group.d.ts
diff --git a/.vscode/typings/react/react-addons-linked-state-mixin.d.ts b/.vscode/typings/react/react-addons-linked-state-mixin.d.ts
diff --git a/.vscode/typings/react/react-addons-perf.d.ts b/.vscode/typings/react/react-addons-perf.d.ts
diff --git a/.vscode/typings/react/react-addons-pure-render-mixin.d.ts b/.vscode/typings/react/react-addons-pure-render-mixin.d.ts
diff --git a/.vscode/typings/react/react-addons-test-utils.d.ts b/.vscode/typings/react/react-addons-test-utils.d.ts
diff --git a/.vscode/typings/react/react-addons-transition-group.d.ts b/.vscode/typings/react/react-addons-transition-group.d.ts
diff --git a/.vscode/typings/react/react-addons-update.d.ts b/.vscode/typings/react/react-addons-update.d.ts
diff --git a/.vscode/typings/react/react-dom.d.ts b/.vscode/typings/react/react-dom.d.ts
diff --git a/.vscode/typings/react/react-global.d.ts b/.vscode/typings/react/react-global.d.ts
diff --git a/.vscode/typings/react/react.d.ts b/.vscode/typings/react/react.d.ts
diff --git a/COLLABORATORS.md b/COLLABORATORS.md
@@ -0,0 +1,22 @@
+# Apollo OSS Collaborator Guidelines
+
+Thanks for helping make Apollo OSS better! Here are a few quick repo maintenance guidelines intended to help keep Apollo projects happy and healthy.
+
+## Overall
+
+- Please remember to be polite and respectful to all community members, no matter what is being reported, contributed, etc. People who are taking time out of their lives to participate in the Apollo ecosystem should feel welcomed, included and appreciated.
+
+## Issues
+
+- Issues are for bugs and feature requests only. All other requests should be redirected accordingly, then closed. Requests for help should go to [Slack](https://www.apollographql.com/slack) or [Stack Overflow](http://stackoverflow.com).
+- If a bug report is valid, add the `confirmed` label, and optionally decide if community help should be requested using the `help-wanted` label. If you’re planning on working on it, assign the issue to yourself.
+- If an issue isn’t easily reproducible, ask for a reproduction and add a `reproduction-needed` label.
+- If a reproduction has been asked for but hasn’t been received in 1 week, close the issue.
+
+## Pull Requests
+
+* Ensure PR’s have tests (when it makes sense, which is almost always).
+* Make sure `CHANGELOG`’s are updated/maintained. Either request that the PR author adds a `CHANGELOG` entry, or add one yourself. Make sure the PR is referenced along with their GitHub username, and link to their profile (to give them extra kudos).
+* Don’t forget to consider how a PR you’re merging will affect the docs; either ask contributors for docs changes, open a new issue to track outstanding changes, or consider implementing the docs changes yourself.
+* Always think about backwards compatibility; please don’t merge PR’s that require major version bumps, unless talking it over with the core team.
+* If the PR has a small number of commits, or a large number of semantically unimportant commits, squash and merge the PR. If the PR commits are well thought out, isolated and would add value to the git history if kept separate, do a merge commit.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -4,7 +4,7 @@ Excited about Apollo and want to make it better? We’re excited too!
 
 Apollo is a community of developers just like you, striving to create the best tools and libraries around GraphQL. We welcome anyone who wants to contribute or provide constructive feedback, no matter the age or level of experience. If you want to help but don't know where to start, let us know, and we'll find something for you.
 
-Oh, and if you haven't already, sign up for the [Apollo Slack](http://www.apollodata.com/#slack).
+Oh, and if you haven't already, sign up for the [Apollo Spectrum](https://spectrum.chat/apollo).
 
 Here are some ways to contribute to the project, from easiest to most difficult:
 
@@ -27,7 +27,7 @@ While we will try to be as helpful as we can on any issue reported, please inclu
 2. **Actual outcome:** A description of what actually happened, including a screenshot or copy-paste of any related error messages, logs, or other output that might be related. Places to look for information include your browser console, server console, and network logs. Please avoid non-specific phrases like “didn’t work” or “broke”.
 3. **How to reproduce the issue:** Instructions for how the issue can be reproduced by a maintainer or contributor. Be as specific as possible, and only mention what is necessary to reproduce the bug. If possible, try to isolate the exact circumstances in which the bug occurs and avoid speculation over what the cause might be.
 
-Creating a good reproduction really helps contributors investigate and resolve your issue quickly. In many cases, the act of creating a minimal reproduction illuminates that the source of the bug was somewhere outside the library in question, saving time and effort for everyone. 
+Creating a good reproduction really helps contributors investigate and resolve your issue quickly. In many cases, the act of creating a minimal reproduction illuminates that the source of the bug was somewhere outside the library in question, saving time and effort for everyone.
 
 Include in the issue a link to your reproduction—a couple good options are a small Github repo or a [CodeSandbox](https://codesandbox.io/). Here's a starter CodeSandbox you can use: https://codesandbox.io/s/yrwE7pvJ7
 
@@ -37,6 +37,8 @@ If you have a more complicated issue where it is helpful to run it locally, you
 
 Improving the documentation, examples, and other open source content can be the easiest way to contribute to the library. If you see a piece of content that can be better, open a PR with an improvement, no matter how small! If you would like to suggest a big change or major rewrite, we’d love to hear your ideas but please open an issue for discussion before writing the PR.
 
+Improving the documentation, examples, and other open source content can be the easiest way to contribute to the library. If you see a piece of content that can be better, open a PR with an improvement, no matter how small! If you would like to suggest a big change or major rewrite, we’d love to hear your ideas! Please open a feature request for discussion, over in the [Apollo Feature Request repo](https://github.com/apollographql/apollo-feature-requests), before writing the PR.
+
 ### Responding to issues
 
 In addition to reporting issues, a great way to contribute to Apollo is to respond to other peoples' issues and try to identify the problem or help them work around it. If you’re interested in taking a more active role in this process, please go ahead and respond to issues. And don't forget to say "Hi" on Apollo Slack!
@@ -45,28 +47,22 @@ In addition to reporting issues, a great way to contribute to Apollo is to respo
 
 For a small bug fix change (less than 20 lines of code changed), feel free to open a pull request. We’ll try to merge it as fast as possible and ideally publish a new release on the same day. The only requirement is, make sure you also add a test that verifies the bug you are trying to fix.
 
-### Suggesting features
-
-Most of the features in Apollo came from suggestions by you, the community! We welcome any ideas about how to make Apollo  better for your use case. Unless there is overwhelming demand for a feature, it might not get implemented immediately, but please include as much information as possible that will help people have a discussion about your proposal:
-
-1. **Use case:** What are you trying to accomplish, in specific terms? Often, there might already be a good way to do what you need and a new feature is unnecessary, but it’s hard to know without information about the specific use case.
-2. **Could this be a plugin?** In many cases, a feature might be too niche to be included in the core of a library, and is better implemented as a companion package. If there isn’t a way to extend the library to do what you want, could we add additional plugin APIs? It’s important to make the case for why a feature should be part of the core functionality of the library.
-3. **Is there a workaround?** Is this a more convenient way to do something that is already possible, or is there some blocker that makes a workaround unfeasible?
+### Suggesting feature
 
-Feature requests will be labeled as such, and we encourage using GitHub issues as a place to discuss new features and possible implementation designs. Please refrain from submitting a pull request to implement a proposed feature until there is consensus that it should be included. This way, you can avoid putting in work that can’t be merged in.
+Most of the features in React Apollo came from suggestions by you, the community! We welcome any ideas about how to make Apollo better for your use case. Head on over to the [Apollo Feature Request repo](https://github.com/apollographql/apollo-feature-requests), and open up a new feature request / discussion issue with your details.
 
-Once there is a consensus on the need for a new feature, proceed as listed below under “Big PRs”.
+**Note:** Feature requests and non-bug related discussions are no longer managed in this repo's issue tracker. Feature request and/or discussions opened here will be closed.
 
 ## Big PRs
 
 This includes:
 
-- Big bug fixes
-- New features
+* Big bug fixes
+* New features
 
 For significant changes to a repository, it’s important to settle on a design before starting on the implementation. This way, we can make sure that major improvements get the care and attention they deserve. Since big changes can be risky and might not always get merged, it’s good to reduce the amount of possible wasted effort by agreeing on an implementation design/plan first.
 
-1. **Open an issue.** Open an issue about your bug or feature, as described above.
+1. **Open an issue.** Open an issue about your bug in this repo, or about your feature request in the [Apollo Feature Request repo](https://github.com/apollographql/apollo-feature-requests).
 2. **Reach consensus.** Some contributors and community members should reach an agreement that this feature or bug is important, and that someone should work on implementing or fixing it.
 3. **Agree on intended behavior.** On the issue, reach an agreement about the desired behavior. In the case of a bug fix, it should be clear what it means for the bug to be fixed, and in the case of a feature, it should be clear what it will be like for developers to use the new feature.
 4. **Agree on implementation plan.** Write a plan for how this feature or bug fix should be implemented. What modules need to be added or rewritten? Should this be one pull request or multiple incremental improvements? Who is going to do each part?

diff --git a/Changelog.md b/Changelog.md
diff --git a/LICENSE b/LICENSE
@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015 Ben Newman
+Copyright (c) 2019 Meteor Development Group, Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

diff --git a/README.md b/README.md
@@ -1,136 +1,36 @@
-# [React Apollo](http://dev.apollodata.com/react/) [![npm version](https://badge.fury.io/js/react-apollo.svg)](https://badge.fury.io/js/react-apollo) [![Get on Slack](https://img.shields.io/badge/slack-join-orange.svg)](http://www.apollostack.com/#slack)
+# <a href="https://www.apollographql.com/"><img src="https://user-images.githubusercontent.com/841294/53402609-b97a2180-39ba-11e9-8100-812bab86357c.png" height="100" alt="React Apollo"></a>
 
-React Apollo allows you to fetch data from your GraphQL server and use it in building complex and reactive UIs using the React framework. React Apollo may be used in any context that React may be used. In the browser, in React Native, or in Node.js when you want to server side render.
+## React Apollo
 
-React Apollo unlike many other tools in the React ecosystem requires _no_ complex build setup to get up and running. As long as you have a GraphQL server you can get started building out your application with React immeadiately. React Apollo works out of the box with both [`create-react-app`][] and [React Native][] with a single install and with no extra hassle configuring Babel or other JavaScript tools.
+[![npm version](https://badge.fury.io/js/react-apollo.svg)](https://badge.fury.io/js/react-apollo)
+[![Build Status](https://circleci.com/gh/apollographql/react-apollo.svg?style=svg)](https://circleci.com/gh/apollographql/react-apollo)
+[![Join the community on Spectrum](https://withspectrum.github.io/badge/badge.svg)](https://spectrum.chat/apollo)
 
-[`create-react-app`]: https://github.com/facebookincubator/create-react-app
-[React Native]: http://facebook.github.io/react-native
+---
 
-React Apollo is:
+⚠️ **THIS PROJECT HAS BEEN DEPRECATED** ⚠️
 
-1. **Incrementally adoptable**, so that you can drop it into an existing JavaScript app and start using GraphQL for just part of your UI.
-2. **Universally compatible**, so that Apollo works with any build setup, any GraphQL server, and any GraphQL schema.
-2. **Simple to get started with**, you can start loading data right away and learn about advanced features later.
-3. **Inspectable and understandable**, so that you can have great developer tools to understand exactly what is happening in your app.
-4. **Built for interactive apps**, so your users can make changes and see them reflected in the UI immediately.
-4. **Small and flexible**, so you don't get stuff you don't need. The core is under 25kb compressed.
-5. **Community driven**, Apollo is driven by the community and serves a variety of use cases. Everything is planned and developed in the open.
+Please note that 4.0.0 is the final version of all React Apollo packages. React Apollo functionality is now directly available from `@apollo/client` >= 3. While using the `@apollo/react-X` packages will still work, we recommend using the following imports from `@apollo/client` directly instead:
+>
+> - old: `@apollo/react-components` --> new: `@apollo/client/react/components`
+> - old: `@apollo/react-hoc` --> new: `@apollo/client/react/hoc`
+> - old: `@apollo/react-ssr` --> new: `@apollo/client/react/ssr`
+> - old: `@apollo/react-testing` --> new: `@apollo/client/testing`
+> - old: `@apollo/react-hooks` --> new: `@apollo/client`
 
-Get started today on the app you’ve been dreaming of, and let React Apollo take you to the moon!
+Moving forward, all Apollo + React issues / pull requests should be opened in the [apollo-client](https://github.com/apollographql/apollo-client.git) repo. Please refer to the [Apollo Client migration guide](https://www.apollographql.com/docs/react/migrating/apollo-client-3-migration/) for more details.
 
-## Installation
+---
 
-It is simple to install React Apollo.
-
-```bash
-npm install react-apollo --save
-```
-
-That’s it! You may now use React Apollo in any of your React environments.
-
-For an amazing developer experience you may also install the [Apollo Client Developer tools for Chrome][] which will give you inspectability into your React Apollo data.
-
-[Apollo Client Developer tools for Chrome]: https://chrome.google.com/webstore/detail/apollo-client-developer-t/jdkknkkbebbapilgoeccciglkfbmbnfm
-
-## Usage
-
-To get started you will first want to create an instance of [`ApolloClient`][] and then you will want to provide that client to your React component tree using the [`<ApolloProvider/>`][] component. Finally, we will show you a basic example of connecting your GraphQL data to your React components with the [`graphql()`][] enhancer function.
-
-First we want an instance of [`ApolloClient`][]. We can import the class from `react-apollo` and construct it like so:
-
-```js
-import { ApolloClient } from 'react-apollo';
-
-const client = new ApolloClient();
-```
-
-This will create a new client that you can use for all of your GraphQL data fetching needs, but most of the time you will also want to create your own custom network interface. By default Apollo Client guesses that your GraphQL API lives at `/graphql`, but this is not always the case. To use your own network interface you may call the [`createNetworkInterface`][] function:
-
-```js
-import { ApolloClient, createNetworkInterface } from 'react-apollo';
-
-const client = new ApolloClient({
-  networkInterface: createNetworkInterface({
-    uri: 'https://graphql.example.com',
-  }),
-});
-```
-
-Replace `https://graphql.example.com` with your GraphQL API’s URL to connect to your API.
-
-Next you will want to add a [`<ApolloProvider/>`][] component to the root of your React component tree. This component works almost the same as the [`<Provider/>` component in `react-redux`][]. In fact if you pass a `store` prop into [`<ApolloProvider/>`][] it will also serve as a provider for `react-redux`! To use an [`<ApolloProvider/>`][] with your newly constructed client see the following:
-
-```js
-import { ApolloProvider } from 'react-apollo';
-
-ReactDOM.render(
-  <ApolloProvider client={client}>
-    <MyRootComponent/>
-  </ApolloProvider>,
-  document.getElementById('root'),
-);
-```
-
-Now you may create components in this React tree that are connected to your GraphQL API.
-
-Finally, to demonstrate the power of React Apollo in building interactive UIs let us connect one of your component’s to your GraphQL server using the [`graphql()`][] component enhancer:
-
-```js
-import { gql, graphql } from 'react-apollo';
-
-function TodoApp({ data: { todos, refetch } }) {
-  return (
-    <div>
-      <button onClick={() => refetch()}>
-        Refresh
-      </button>
-      <ul>
-        {todos.map(todo => (
-          <li key={todo.id}>
-            {todo.text}
-          </li>
-        ))}
-      </ul>
-    </div>
-  );
-}
-
-export default graphql(gql`
-  query TodoAppQuery {
-    todos {
-      id
-      text
-    }
-  }
-`)(TodoApp);
-```
-
-With that your `<TodoApp/>` component is now connected to your GraphQL API. Whenever some other component modifies the data in your cache, this component will automatically be updated with the new data.
-
-To learn more about querying with React Apollo be sure to start reading the [documentation article on Queries][]. If you would like to see all of the features React Apollo supports be sure to check out the [complete API reference][].
-
-There is also an excellent [**Full-stack React + GraphQL Tutorial**][] on the Apollo developer blog.
-
-[`ApolloClient`]: http://dev.apollodata.com/core/apollo-client-api.html#apollo-client
-[`<ApolloProvider/>`]: http://dev.apollodata.com/react/api.html#ApolloProvider
-[`graphql()`]: http://dev.apollodata.com/react/api.html#graphql
-[`createNetworkInterface`]: http://dev.apollodata.com/core/network.html
-[`<Provider/>` component in `react-redux`]: https://github.com/reactjs/react-redux/blob/master/docs/api.md#provider-store
-[documentation article on Queries]: http://dev.apollodata.com/react/queries.html
-[complete API reference]: http://dev.apollodata.com/react/api.html
-[**Full-stack React + GraphQL Tutorial**]: https://dev-blog.apollodata.com/full-stack-react-graphql-tutorial-582ac8d24e3b#.w8e9j7jmp
-[Learn Apollo]: https://www.learnapollo.com/
+React Apollo allows you to fetch data from your GraphQL server and use it in building complex and reactive UIs using the React framework. React Apollo may be used in any context that React may be used. In the browser, in React Native, or in Node.js when you want to do server-side rendering.
 
 ## Documentation
 
-For a complete React Apollo API reference visit the documentation website at: [http://dev.apollodata.com/react/api.html](http://dev.apollodata.com/react/api.html)
+All Apollo Client documentation, including React Apollo usage articles and helpful recipes, lives on [https://www.apollographql.com/docs/react/](https://www.apollographql.com/docs/react/)
 
-All of the documentation for React Apollo including usage articles and helpful recipes lives on: [http://dev.apollodata.com/react/](http://dev.apollodata.com/react/)
+For the React Apollo API reference, visit [https://www.apollographql.com/docs/react/api/react-apollo.html](https://www.apollographql.com/docs/react/api/react-apollo.html)
 
-### Recipes
+## Maintainers
 
-- [Authentication](http://dev.apollodata.com/react/auth.html)
-- [Pagination](http://dev.apollodata.com/react/pagination.html)
-- [Optimistic UI](http://dev.apollodata.com/react/optimistic-ui.html)
-- [Server Side Rendering](http://dev.apollodata.com/react/server-side-rendering.html)
+- [@benjamn](https://github.com/benjamn) (Apollo)
+- [@hwillson](https://github.com/hwillson) (Apollo)
diff --git a/appveyor.yml b/appveyor.yml
diff --git a/dangerfile.ts b/dangerfile.ts
diff --git a/examples/create-react-app/.flowconfig b/examples/create-react-app/.flowconfig
diff --git a/examples/create-react-app/.gitignore b/examples/create-react-app/.gitignore
diff --git a/examples/create-react-app/README.md b/examples/create-react-app/README.md
diff --git a/examples/create-react-app/package.json b/examples/create-react-app/package.json
diff --git a/examples/create-react-app/public/favicon.ico b/examples/create-react-app/public/favicon.ico
diff --git a/examples/create-react-app/public/index.html b/examples/create-react-app/public/index.html
diff --git a/examples/create-react-app/src/App.js b/examples/create-react-app/src/App.js
diff --git a/examples/create-react-app/src/App.test.js b/examples/create-react-app/src/App.test.js
diff --git a/examples/create-react-app/src/Pokemon.js b/examples/create-react-app/src/Pokemon.js
diff --git a/examples/create-react-app/src/Pokemon.test.js b/examples/create-react-app/src/Pokemon.test.js
diff --git a/examples/create-react-app/src/__snapshots__/Pokemon.test.js.snap b/examples/create-react-app/src/__snapshots__/Pokemon.test.js.snap
diff --git a/examples/create-react-app/src/index.js b/examples/create-react-app/src/index.js
diff --git a/examples/create-react-app/yarn.lock b/examples/create-react-app/yarn.lock
diff --git a/examples/meteor/.gitignore b/examples/meteor/.gitignore
diff --git a/examples/meteor/.meteor/.finished-upgraders b/examples/meteor/.meteor/.finished-upgraders
diff --git a/examples/meteor/.meteor/.gitignore b/examples/meteor/.meteor/.gitignore
diff --git a/examples/meteor/.meteor/.id b/examples/meteor/.meteor/.id
diff --git a/examples/meteor/.meteor/packages b/examples/meteor/.meteor/packages
diff --git a/examples/meteor/.meteor/platforms b/examples/meteor/.meteor/platforms
diff --git a/examples/meteor/.meteor/release b/examples/meteor/.meteor/release
diff --git a/examples/meteor/.meteor/versions b/examples/meteor/.meteor/versions
diff --git a/examples/meteor/client/index.js b/examples/meteor/client/index.js
diff --git a/examples/meteor/client/main.html b/examples/meteor/client/main.html
diff --git a/examples/meteor/imports/App.js b/examples/meteor/imports/App.js
diff --git a/examples/meteor/imports/Pokemon.js b/examples/meteor/imports/Pokemon.js
diff --git a/examples/meteor/package.json b/examples/meteor/package.json
diff --git a/examples/meteor/server/index.js b/examples/meteor/server/index.js
diff --git a/examples/react-native/.babelrc b/examples/react-native/.babelrc
diff --git a/examples/react-native/.buckconfig b/examples/react-native/.buckconfig
diff --git a/examples/react-native/.flowconfig b/examples/react-native/.flowconfig
diff --git a/examples/react-native/.gitignore b/examples/react-native/.gitignore
diff --git a/examples/react-native/.watchmanconfig b/examples/react-native/.watchmanconfig
diff --git a/examples/react-native/Pokemon.js b/examples/react-native/Pokemon.js
diff --git a/examples/react-native/__tests__/index.android.js b/examples/react-native/__tests__/index.android.js
diff --git a/examples/react-native/__tests__/index.ios.js b/examples/react-native/__tests__/index.ios.js
diff --git a/examples/react-native/android/app/BUCK b/examples/react-native/android/app/BUCK
diff --git a/examples/react-native/android/app/build.gradle b/examples/react-native/android/app/build.gradle
diff --git a/examples/react-native/android/app/proguard-rules.pro b/examples/react-native/android/app/proguard-rules.pro
diff --git a/examples/react-native/android/app/src/main/AndroidManifest.xml b/examples/react-native/android/app/src/main/AndroidManifest.xml
diff --git a/examples/react-native/android/app/src/main/java/com/reactnative/MainActivity.java b/examples/react-native/android/app/src/main/java/com/reactnative/MainActivity.java
diff --git a/examples/react-native/android/app/src/main/java/com/reactnative/MainApplication.java b/examples/react-native/android/app/src/main/java/com/reactnative/MainApplication.java
diff --git a/examples/react-native/android/app/src/main/res/mipmap-hdpi/ic_launcher.png b/examples/react-native/android/app/src/main/res/mipmap-hdpi/ic_launcher.png
diff --git a/examples/react-native/android/app/src/main/res/mipmap-mdpi/ic_launcher.png b/examples/react-native/android/app/src/main/res/mipmap-mdpi/ic_launcher.png
diff --git a/examples/react-native/android/app/src/main/res/mipmap-xhdpi/ic_launcher.png b/examples/react-native/android/app/src/main/res/mipmap-xhdpi/ic_launcher.png
diff --git a/examples/react-native/android/app/src/main/res/mipmap-xxhdpi/ic_launcher.png b/examples/react-native/android/app/src/main/res/mipmap-xxhdpi/ic_launcher.png
diff --git a/examples/react-native/android/app/src/main/res/values/strings.xml b/examples/react-native/android/app/src/main/res/values/strings.xml
diff --git a/examples/react-native/android/app/src/main/res/values/styles.xml b/examples/react-native/android/app/src/main/res/values/styles.xml
diff --git a/examples/react-native/android/build.gradle b/examples/react-native/android/build.gradle
diff --git a/examples/react-native/android/gradle.properties b/examples/react-native/android/gradle.properties
diff --git a/examples/react-native/android/gradle/wrapper/gradle-wrapper.jar b/examples/react-native/android/gradle/wrapper/gradle-wrapper.jar
diff --git a/examples/react-native/android/gradle/wrapper/gradle-wrapper.properties b/examples/react-native/android/gradle/wrapper/gradle-wrapper.properties
diff --git a/examples/react-native/android/gradlew b/examples/react-native/android/gradlew
diff --git a/examples/react-native/android/gradlew.bat b/examples/react-native/android/gradlew.bat
diff --git a/examples/react-native/android/keystores/BUCK b/examples/react-native/android/keystores/BUCK
diff --git a/examples/react-native/android/keystores/debug.keystore.properties b/examples/react-native/android/keystores/debug.keystore.properties
diff --git a/examples/react-native/android/settings.gradle b/examples/react-native/android/settings.gradle
diff --git a/examples/react-native/index.ios.js b/examples/react-native/index.ios.js
diff --git a/examples/react-native/ios/reactnative.xcodeproj/project.pbxproj b/examples/react-native/ios/reactnative.xcodeproj/project.pbxproj
diff --git a/examples/react-native/ios/reactnative.xcodeproj/xcshareddata/xcschemes/reactnative.xcscheme b/examples/react-native/ios/reactnative.xcodeproj/xcshareddata/xcschemes/reactnative.xcscheme
diff --git a/examples/react-native/ios/reactnative/AppDelegate.h b/examples/react-native/ios/reactnative/AppDelegate.h
diff --git a/examples/react-native/ios/reactnative/AppDelegate.m b/examples/react-native/ios/reactnative/AppDelegate.m
diff --git a/examples/react-native/ios/reactnative/Base.lproj/LaunchScreen.xib b/examples/react-native/ios/reactnative/Base.lproj/LaunchScreen.xib
diff --git a/examples/react-native/ios/reactnative/Images.xcassets/AppIcon.appiconset/Contents.json b/examples/react-native/ios/reactnative/Images.xcassets/AppIcon.appiconset/Contents.json
diff --git a/examples/react-native/ios/reactnative/Info.plist b/examples/react-native/ios/reactnative/Info.plist
diff --git a/examples/react-native/ios/reactnative/main.m b/examples/react-native/ios/reactnative/main.m
diff --git a/examples/react-native/ios/reactnativeTests/Info.plist b/examples/react-native/ios/reactnativeTests/Info.plist
diff --git a/examples/react-native/ios/reactnativeTests/reactnativeTests.m b/examples/react-native/ios/reactnativeTests/reactnativeTests.m
diff --git a/examples/react-native/package.json b/examples/react-native/package.json