* Cache No-Revalidate Pages

* Specifically check for `false`

Instead of `canary`. React uses `next` to represent the next
minor release.

* Upgrade Lockfile

* Fix types version mismatch

* Upgrade amphtml-validator

* Revert "Upgrade amphtml-validator"

This reverts commit 05068b2ad9f2f53429cf514b47b4f7924b0b9623.

* Disable AMP Tests

* Skip 2x more AMP tests

* Test `react(-dom)@canary` Every 12 Hours

* Use POSIX syntax

* Test

* Revert "Test"

This reverts commit ba5f22f0b0a2255613b8f11af84581722ad2ca7a.

* Print react versions prior to test

* Revert "Revert "Test""

This reverts commit 0b3cde3c4226066309561ca7c9e684070999af32.

* Revert "Revert "Revert "Test"""

This reverts commit c2c284a7a8d6dc9f39c6d16df109da3ed402afdf.

* Upgrade React dependencies

* Disable data tests

* Increase allowed default sizes

* add netlifycms example

* Updated everything

* Moved the layout out of _app

* Updated next to latest

* applied prettier and linter

* Removed unrequired files

* Moved to with-netlify-cms

* updated readme to reflect the new name

* Added license field

* Warn on No Cache in CI

* Bold the note lead

* Add custom clarification for netlify

* Reorder

* Add tests

* Fix detection

* allow to remove amphtml from desktop page

* only 1 link with amphtml rel

* clean up

* remove checkup for amphtml link

* Dedupe looping

* Register page export declaration to scope

* Update to not need to traverse to update scope

## Changelog

- Use functional components instead of class components
- Use default exports like in all other examples
- Rename `Portal` component to `ClientOnlyPortal`.

* Dedupe meta tag in favor of custom tag defined in _app

* Add test

* Fix comments

## Changelog

- Remove `getInitialProps`
- Explain variants
- Reflect latest changes in the prefetch api
- Update UI

* Don't mark page as nextExport if it's SPR

* Add test for fetching prerender data after mount

* Add the example of tailwindcss with emotion

* Add README.md

* Fix Unexpected trailing comma.

* Update the readme, and use latest Next.js version

* Update to return json if data request

* Update sending data

* Add test using serverless bundle directly

* Don't early return if fromExport

* [with-typescript] Updated TypeScript example to use API routes

Next.js 9.0.0 has been out for a while, which supports API routes, but
the examples were never updated to make use of it. This PR adds a simple
example of an API route which also makes use of dynamic routing.

A simple `fetch()` wrapper is also added for example purposes, and the
pages structure have also been updated to dynamic routing.

* Properly link to the dynamic page

* Update inferno examples to v7.3

* Add polyfill for React.createContext

* Alias react and react-dom with inferno-compat

* Fix linter errors

* Add warning about hooks and suspense support

## Changelog

- Removed react-lazyload
- Removed images
- Removed ReactDOMServer from Client
- Removed next.config.js

## Notes

**CommonJS vs ESM:** In the future we might be able to use top level `await` in order to import only on the server (e.g.: `await import(“react-dom/server”)`)

Until then we need to mix CommonJS and ESM in favor of messing with the webpack config.

The call to `accept.languages()` made the fallback not work.
When called e.g. with `Accept-Language: es-ES,es;q=0.9`, `locale` would contain `[ 'es-ES', 'es' ]` instead of `en`.

(See also: https://www.npmjs.com/package/accepts#languagelanguages )

* Update preact example with Preact X

* Update README

* Update _document.tsx to optimize script loading

* Update maxInitialChunks to 15

* Undo change chunk count

* Adjust impl a bit

* Add CSS preload test

* Ensure build manifest not preloaded

* Correct file name

* break comment

* Add failing tests for SPR

* Fix SPR always revalidating in production

* Remove extra changes

This pull request is a temporary addition that uses the `x-now-route-params` header in serverless.

This header returns the regex groups with indexes, not their named variants.
As a result, we must use the getRouteMatcher utility to reverse this into Next.js' expected names.

Since this got complex, I've added a test for it. We should probably remove this behavior sooner than later.

This pins chromedriver to the version specified in https://github.com/Microsoft/azure-pipelines-image-generation/blob/master/images/win/Vs2017-Server2016-Readme.md.