Just a minor typo fix: `Github` -> `GitHub`.

Not sure when it was introduced, but on the latest Next v8.0.4, there's no descriptive name attached to the component returns from `withRouter`.

This makes it harder to debug and write test cases for components wrapped by `withRouter`.

* Only refresh the page when the active
page is updated in AMP mode

* Update handling of page reload to make sure it
still refreshes after a change to another page

* Update checking to be more accurate

* Fix amp-dev not being loaded without
experimental.amp and remove next.config from amp example

* Remove old with-amp example and
rename experimental-amp to with-amp

* update example name
Co-Authored-By: Nijjk <jj@jjsweb.site>

* Update comment wording
Co-Authored-By: Nijjk <jj@jjsweb.site>

* Use document for reload to keep scroll position
Co-Authored-By: Nijjk <jj@jjsweb.site>

* fallback to reloading on error
Co-Authored-By: Nijjk <jj@jjsweb.site>

* Update with-amp example readme

* Make sure AmpContext is available during _document
render and update filtering of script tags in AMP mode

* Update amphtml test to make sure
AmpContext is set for _document render

* Fix stray comma in render.tsx

* Add WithAmp to enable AMP support for
pages instead of .amp.js

* Update handling for exporting AMP

* Fix ampPath in export for / path and
revert isAmp logic to handle right

* Update amphtml test suite

* Add handling for noDirtyAmp during
export and update amp-export test suite

* Update serverless and export-default-map
test suites

* Update require-page tests

This skips re-compressing already minified files.

* Make async-to-promises babel plugin experimental

* Move excludes for asyncToPromises behind flag too

* Move other configs behind flag

* Re-add original exclude item

I'm using this to profile right now, so it's probably good to update it.

* Set custom cacheIdentifier for babel-
loader that we can increment

* Update to consider external babel config
for cacheIdentifier

* Update to follow babel loader's cacheIdentifier behavior

* Add Flying Shuttle tests

* Test second version of server

* Finish first version of tests

* Apply suggestions from code review
Co-Authored-By: NTimer <timer150@gmail.com>

* Apply suggestions from code review
Co-Authored-By: NTimer <timer150@gmail.com>

* Use next.config env and packages to calculate
hashes for chunk-graph

* Remove example from testing

* remove left over import

* Tweak behavior

* Add Flying Shuttle v1

* Add serverless file restoration

* Add another message

* Update test

* Resolve page version last

* Print number of changed pages

* Remove old tests

* Re-add head build ID writing

* Change syntax appearance

* Start adding test components

* Fix react loadable manifest

* Complicate dynamic testing

* Fix first build missing head build id

* Remove flying shuttle tests

We cannot rely on `recordsPath` when using selective page mode. All modules must be identified.

This fixes a case where a user has a page named `next.js.js` and `next.js`.

This output clashed with the new output style. This output is more inline with existing behavior.

* Move build utils to their own file

* Tweak feature detection

* Remove CLI and negative page building

* Remove select all tests

* Update test of getSpecifiedPages

* Prune old tests from snapshot

* Remove old flying shuttle tests

* Fix re-rendering on client after navigating
back from external site

* Clean up tagging before unload

* Add check for history.state 1/2
Co-Authored-By: Nijjk <22380829+ijjk@users.noreply.github.com>

* Add check for history.state 2/2
Co-Authored-By: Nijjk <22380829+ijjk@users.noreply.github.com>

* Add check for options
Co-Authored-By: Nijjk <22380829+ijjk@users.noreply.github.com>

* Add test for navigating to external site and back
also added testing in safari and firefox

* Add test for query in url

Added [cross-env](https://www.npmjs.com/package/cross-env) package for using the command `npm start` on Windows environment.

Tested on:
- [x] Windows version 1809
- [x] Node.js 10.15.3 (LTS version)

While implementing hapi as a custom server, I found a minor issue. The example provided isn't showing that we also need to serve static files using next. This change should fix that. Thanks!

`router` is not needed in the scope

- fix runtime configuration example to use `customKey`
- standardize warning callouts to use a block quote and bold "**Warning:**" text. Previously there were different ways a warning was mentioned on the docs page:
  - A warning emoji. The warning emoji didn't render in the actual site.
    <img width="770" alt="Screen Shot 2019-03-21 at 9 22 21 AM" src="https://user-images.githubusercontent.com/1103708/54759302-c655f380-4bbb-11e9-9116-b0fdc2467bc3.png">
  - Italicized "Warning" text. Imo, does not stand out on the page.
    <img width="663" alt="Screen Shot 2019-03-21 at 9 24 43 AM" src="https://user-images.githubusercontent.com/1103708/54759376-f604fb80-4bbb-11e9-85c6-6589b7738dee.png">