Update apollo pure (#1762)

* C++ build env is not necessary

* Support Node v12 and Stable

* Update deps

* Prettier **/*.md

```
find . -path ./node_modules -prune -o -name '*.md' | xargs yarn prettier --write
```

.travis.yml

@@ -1,16 +1,9 @@
 language: node_js
 node_js:
   - 'stable'
+  - '12'
   - '10'
   - '8'
-env:
-  - CXX=g++-4.8
-addons:
-  apt:
-    sources:
-      - ubuntu-toolchain-r-test
-    packages:
-      - g++-4.8
 cache: yarn
 script:
   - yarn codegen

CHANGELOG.md

@@ -27,13 +27,15 @@ All notable changes to this project will be documented in this file.
 - Move page / screen components into the `src/routes` folder along with the routing information for them (BREAKING CHANGE). [6553936](https://github.com/kriasoft/react-starter-kit/commit/6553936e693e24a8ac6178f4962af15e0ea87dfd)
 
 ### [v0.5.1]
+
 > 2016-03-02
 
 - Remove `Html` React component in favor of compiled Jade templates (`src/views`) (BREAKING CHANGE). [e188388](https://github.com/kriasoft/react-starter-kit/commit/e188388f87069cdc7d501b385d6b0e46c98fed60)
 - Add global error handling in Node.js/Express app. [e188388](https://github.com/kriasoft/react-starter-kit/commit/e188388f87069cdc7d501b385d6b0e46c98fed60)
 - Add support for Markdown and HTML for static pages. [#469](https://github.com/kriasoft/react-starter-kit/pull/469), [#477](https://github.com/kriasoft/react-starter-kit/pull/477)
 
 ### [v0.5.0]
+
 > 2016-02-27
 
 - Replace RESTful API endpoint (`src/api`) with GraphQL (`src/data`)
@@ -54,6 +56,7 @@ All notable changes to this project will be documented in this file.
 - Add `CHANGELOG.md` file with a list of notable changes to this project
 
 ### [v0.4.1]
+
 > 2015-10-04
 
 - Replace React Hot Loader (deprecated) with React Transform

CONTRIBUTING.md

@@ -33,23 +33,23 @@ files right from GitHub website as described [here](https://help.github.com/arti
 
 Before opening an issue, please:
 
-* Check the [Getting Started](https://github.com/kriasoft/react-starter-kit/blob/master/docs/getting-started.md) guide.
-* Search the [issue tracker](https://github.com/kriasoft/react-starter-kit/issues) to make sure
+- Check the [Getting Started](https://github.com/kriasoft/react-starter-kit/blob/master/docs/getting-started.md) guide.
+- Search the [issue tracker](https://github.com/kriasoft/react-starter-kit/issues) to make sure
   your issue hasn’t already been reported.
-* If your issue sounds more like a question, please post it on StackOverflow.com instead with the
+- If your issue sounds more like a question, please post it on StackOverflow.com instead with the
   tag [react-starter-kit](http://stackoverflow.com/questions/tagged/react-starter-kit).
 
 ### Pull Requests
 
 Before you submit a [pull request](https://help.github.com/articles/using-pull-requests/) from your
 forked repo, check that it meets these guidelines:
 
-* If the pull request adds functionality, the docs should be updated as part of the same PR.
-* Create a separate PR for each small feature or bug fix.
-* [Squash](http://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git)
+- If the pull request adds functionality, the docs should be updated as part of the same PR.
+- Create a separate PR for each small feature or bug fix.
+- [Squash](http://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git)
   your commits into one for each PR.
-* Run `yarn test` to make sure that your code style is OK and there are no any regression bugs.
-* When contributing to an opt-in feature, apply the `[feature/...]` tag as a prefix to your PR title
+- Run `yarn test` to make sure that your code style is OK and there are no any regression bugs.
+- When contributing to an opt-in feature, apply the `[feature/...]` tag as a prefix to your PR title
 
 #### Style Guide
 

docs/README.md

@@ -2,20 +2,20 @@
 
 ### General
 
-* [Getting Started](./getting-started.md)
-* [React Style Guide](./react-style-guide.md)
-* [How to configure text editors and IDEs](./how-to-configure-text-editors.md)
-* [Testing your application](./testing-your-application.md)
+- [Getting Started](./getting-started.md)
+- [React Style Guide](./react-style-guide.md)
+- [How to configure text editors and IDEs](./how-to-configure-text-editors.md)
+- [Testing your application](./testing-your-application.md)
 
 ### Questions
 
-* [Which module bundler should I use?](https://github.com/kriasoft/react-starter-kit/issues/3)
-* [Which Flux implementation should I use?](https://github.com/kriasoft/react-starter-kit/issues/22)
+- [Which module bundler should I use?](https://github.com/kriasoft/react-starter-kit/issues/3)
+- [Which Flux implementation should I use?](https://github.com/kriasoft/react-starter-kit/issues/22)
 
 ### Recipes
 
-* [How to Implement Routing and Navigation](./recipes/how-to-implement-routing.md)
-* [How to Integrate React Intl](./recipes/how-to-integrate-react-intl.md)
-* [How to Integrate Disqus](./recipes/how-to-integrate-disqus.md)
-* [How to Use Sass/SCSS](./recipes/how-to-use-sass.md)
-* [How to Configure Facebook Login](./recipes/how-to-configure-facebook-login.md)
+- [How to Implement Routing and Navigation](./recipes/how-to-implement-routing.md)
+- [How to Integrate React Intl](./recipes/how-to-integrate-react-intl.md)
+- [How to Integrate Disqus](./recipes/how-to-integrate-disqus.md)
+- [How to Use Sass/SCSS](./recipes/how-to-use-sass.md)
+- [How to Configure Facebook Login](./recipes/how-to-configure-facebook-login.md)

docs/how-to-configure-text-editors.md

@@ -32,21 +32,21 @@ Enable **CSSComb** by following the instructions
 
 Install atom packages
 
-* [linter](https://atom.io/packages/linter)
-* [linter-eslint](https://atom.io/packages/linter-eslint)
-* [linter-stylelint](https://atom.io/packages/linter-stylelint)
-* [react](https://atom.io/packages/react)
+- [linter](https://atom.io/packages/linter)
+- [linter-eslint](https://atom.io/packages/linter-eslint)
+- [linter-stylelint](https://atom.io/packages/linter-stylelint)
+- [react](https://atom.io/packages/react)
 
 ```shell
 apm install linter linter-eslint react linter-stylelint
 ```
 
 Install local npm packages
 
-* [eslint](https://www.npmjs.com/package/eslint)
-* [babel-eslint](https://www.npmjs.com/package/babel-eslint)
-* [eslint-plugin-react](https://www.npmjs.com/package/eslint-plugin-react)
-* [stylelint](https://www.npmjs.com/package/stylelint)
+- [eslint](https://www.npmjs.com/package/eslint)
+- [babel-eslint](https://www.npmjs.com/package/babel-eslint)
+- [eslint-plugin-react](https://www.npmjs.com/package/eslint-plugin-react)
+- [stylelint](https://www.npmjs.com/package/stylelint)
 
 ```shell
 yarn add --dev eslint babel-eslint eslint-plugin-react stylelint
@@ -60,22 +60,22 @@ Install SublimeText packages\
 Easiest with [Package Control](https://packagecontrol.io/) and then "Package Control:
 Install Package" (Ctrl+Shift+P)
 
-* [Babel](https://packagecontrol.io/packages/Babel)
-* [Sublime-linter](http://www.sublimelinter.com/en/latest/)
-* [SublimeLinter-contrib-eslint](https://packagecontrol.io/packages/SublimeLinter-contrib-eslint)
-* [SublimeLinter-contrib-stylelint](https://packagecontrol.io/packages/SublimeLinter-contrib-stylelint)
+- [Babel](https://packagecontrol.io/packages/Babel)
+- [Sublime-linter](http://www.sublimelinter.com/en/latest/)
+- [SublimeLinter-contrib-eslint](https://packagecontrol.io/packages/SublimeLinter-contrib-eslint)
+- [SublimeLinter-contrib-stylelint](https://packagecontrol.io/packages/SublimeLinter-contrib-stylelint)
 
 You can also use
 [SublimeLinter-contrib-eslint_d](https://packagecontrol.io/packages/SublimeLinter-contrib-eslint_d)
 for faster linting.
 
 Set Babel as default syntax for a particular extension:
 
-* Open a file with that extension,
-* Select `View` from the menu,
-* Then `Syntax` `->` `Open all with current extension as...` `->` `Babel` `->`
+- Open a file with that extension,
+- Select `View` from the menu,
+- Then `Syntax` `->` `Open all with current extension as...` `->` `Babel` `->`
   `JavaScript (Babel)`.
-* Repeat this for each extension (e.g.: .js and .jsx).
+- Repeat this for each extension (e.g.: .js and .jsx).
 
 Install local npm packages
 

docs/recipes/how-to-implement-routing.md

@@ -206,25 +206,25 @@ module that is built around the same concepts demonstrated earlier with the majo
 it supports nested routes and provides you with the helper `Link` React component. It can be seen as
 a lightweight more flexible alternative to React Router.
 
-* It has simple code with minimum dependencies (just `path-to-regexp` and `babel-runtime`)
-* It can be used with any JavaScript framework such as React, Vue.js etc
-* It uses the same middleware approach used in Express and Koa, making it easy to learn
-* It uses the exact same API and implementation to be used in both Node.js and browser environments
+- It has simple code with minimum dependencies (just `path-to-regexp` and `babel-runtime`)
+- It can be used with any JavaScript framework such as React, Vue.js etc
+- It uses the same middleware approach used in Express and Koa, making it easy to learn
+- It uses the exact same API and implementation to be used in both Node.js and browser environments
 
 The [Getting Started page](https://github.com/kriasoft/universal-router/blob/master/docs/getting-started.md)
 has a few examples how to use it.
 
 ### Related Articles
 
-* [You might not need React Router](https://medium.freecodecamp.com/you-might-not-need-react-router-38673620f3d) by Konstantin Tarkus
+- [You might not need React Router](https://medium.freecodecamp.com/you-might-not-need-react-router-38673620f3d) by Konstantin Tarkus
 
 ### Related Projects
 
-* [`path-to-regexp`](https://github.com/pillarjs/path-to-regexp)
-* [`history`](https://github.com/ReactTraining/history)
-* [Universal Router](https://github.com/kriasoft/universal-router)
+- [`path-to-regexp`](https://github.com/pillarjs/path-to-regexp)
+- [`history`](https://github.com/ReactTraining/history)
+- [Universal Router](https://github.com/kriasoft/universal-router)
 
 ### Related Discussions
 
-* [How to Implement Routing and Navigation](https://github.com/kriasoft/react-starter-kit/issues/748)
-* [How to Add a Route to RSK?](https://github.com/kriasoft/react-starter-kit/issues/754)
+- [How to Implement Routing and Navigation](https://github.com/kriasoft/react-starter-kit/issues/748)
+- [How to Add a Route to RSK?](https://github.com/kriasoft/react-starter-kit/issues/754)

docs/recipes/how-to-integrate-react-intl.md

@@ -44,24 +44,24 @@
 
 Just import the appropriate [component](https://github.com/yahoo/react-intl/wiki#the-react-intl-module) from `react-intl`
 
-* For localizable text use
+- For localizable text use
   [`<FormattedMessage>`](https://github.com/yahoo/react-intl/wiki/Components#formattedmessage).
-* You can also use it with
+- You can also use it with
   the [`defineMessages()`](https://github.com/yahoo/react-intl/wiki/API#definemessages) helper.
 
-* For date and time:
+- For date and time:
   [`<FormattedDate>`](https://github.com/yahoo/react-intl/wiki/Components#formatteddate)
   [`<FormattedTime>`](https://github.com/yahoo/react-intl/wiki/Components#formattedtime)
   [`<FormattedRelative>`](https://github.com/yahoo/react-intl/wiki/Components#formattedrelative)
 
-* For numbers and currencies:
+- For numbers and currencies:
   [`<FormattedNumber>`](https://github.com/yahoo/react-intl/wiki/Components#formattednumber)
   [`<FormattedPlural>`](https://github.com/yahoo/react-intl/wiki/Components#formattedplural)
 
-* If possible, do not use `<FormattedHTMLMessage>`, see how to use _Rich Text Formatting_ with
+- If possible, do not use `<FormattedHTMLMessage>`, see how to use _Rich Text Formatting_ with
   [`<FormattedMessage>`](https://github.com/yahoo/react-intl/wiki/Components#formattedmessage)
 
-* When you need an imperative formatting API, use the [`injectIntl`](https://github.com/yahoo/react-intl/wiki/API#injectintl) High-Order Component.
+- When you need an imperative formatting API, use the [`injectIntl`](https://github.com/yahoo/react-intl/wiki/API#injectintl) High-Order Component.
 
 #### Example
 
@@ -128,6 +128,6 @@ When editing a translation file, it should be copied to `build/messages/` direct
 
 ### Other References
 
-* [`Intl documentation on MDN`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Intl)
-* [express-request-language](https://github.com/tinganho/express-request-language#readme)
+- [`Intl documentation on MDN`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Intl)
+- [express-request-language](https://github.com/tinganho/express-request-language#readme)
   – for more details how initial language negotiation works.

docs/testing-your-application.md

@@ -4,31 +4,31 @@
 
 RSK comes with the following libraries for testing purposes:
 
-* [Jest](https://facebook.github.io/jest/) - JavaScript testing library
-* [Enzyme](https://github.com/airbnb/enzyme) - Testing utilities for React
+- [Jest](https://facebook.github.io/jest/) - JavaScript testing library
+- [Enzyme](https://github.com/airbnb/enzyme) - Testing utilities for React
 
 You may also want to take a look at the following related packages:
 
-* [jsdom](https://github.com/tmpvar/jsdom)
-* [react-addons-test-utils](https://www.npmjs.com/package/react-addons-test-utils)
+- [jsdom](https://github.com/tmpvar/jsdom)
+- [react-addons-test-utils](https://www.npmjs.com/package/react-addons-test-utils)
 
 ### Running tests
 
 To test your application simply run the
 [`yarn test`](https://github.com/kriasoft/react-starter-kit/blob/9014614edcb2f44b23298ca3287b9af3a14b6076/package.json#L152)
 command which will:
 
-* recursively find all files ending with `.test.js` in your `src/` directory
+- recursively find all files ending with `.test.js` in your `src/` directory
 
 ```bash
 yarn test
 ```
 
 ### Conventions
 
-* test filenames MUST end with `test.js` or `yarn test` will not be able to
+- test filenames MUST end with `test.js` or `yarn test` will not be able to
   detect them
-* test filenames SHOULD be named after the related component (e.g. create
+- test filenames SHOULD be named after the related component (e.g. create
   `Login.test.js` for `Login.js` component)
 
 ### Basic example