* npx create → npm init

* Fix inconsistent instructions

* Update amp-first

* Update with-graphql-react

* with-firebase-cloud-messaging

* Update with-higher-order-component

* change create-next-app url

* Update create-next-app instruction

* Update instructions to use npm instead of npx

* Move "the idea behind the example" to top

* Rename

* Rename

* Update contributing.md with a README template

* Add an example for Fauna using cookie based auth.

* Update example to use more secure method of non-js cookie and all authed access via backend api calls.

* Updated README

* Updated files and added prettier

* Remove unused import to fix lint issue.

* Improve documentation on how to setup fauna. Remove client key to simplify setup.

* Remove semicolons

* Lint fix

* Updated readme instructions and deployment

* Fixed client side redirect issue with /profile

* Simplified login code

* Simplified signup code

* Removed isomorphic-unfetch

* Simplified logout

* Removed get-host file

* Removed the custom getInitialProps from withAuthSync

* Removed user email from localStorage
Co-authored-by: NLuis Alvarez D. <luis@zeit.co>

* Added with-styled-components-rtl example

* Add idea behing the example
Co-authored-by: NJoe Haddad <timer150@gmail.com>

I think `httpOnly` property should set as `cookie`'s property.
This is because `SessionOptions` is following.

```
  interface SessionOptions {
    secret: string | string[];
    name?: string;
    store?: Store | MemoryStore;
    cookie?: {
      maxAge?: number;
      signed?: boolean;
      expires?: Date;
      httpOnly?: boolean;
      path?: string;
      domain?: string;
      secure?: boolean | 'auto';
      encode?: (val: string) => string;
      sameSite?: boolean | 'lax' | 'strict' | 'none';
    };
    genid?(req: express.Request): string;
    rolling?: boolean;
    resave?: boolean;
    proxy?: boolean;
    saveUninitialized?: boolean;
    unset?: string;
  }
```

* add with-chakra-ui example

* lint
Co-authored-by: NJoe Haddad <timer150@gmail.com>

* Update tailwind example

* Update blog-starter example

* Update with-next-css example

* Update with-quill-js

* Update with-rbx-bulma-pro

* Remove incompatible example

* Update with-react-multi-carousel

* Update-with-semantic-ui

* Update with-videojs example

* Remove @zeit/next-css from package.json of updated examples

* Remove deprecated examples

* Remove target from all examples

* Update package.json

* Apply suggestions from code review
Co-Authored-By: NJoe Haddad <timer@zeit.co>
Co-authored-by: NJoe Haddad <timer150@gmail.com>

**npm** section currently shows both npm and yarn, while **yarn** section shows just npm.

Co-authored-by: NLuis Alvarez D. <luis@zeit.co>

* New example with-typescript-graphql

* Update newer graphql-let

* Apply @lfades 's suggestions

* Use "lib" for tools directory
* Move config decorator to next.config.js
* Apply stricter tsconfig
* mod: hide the word "apollo" from users

* mod: Use variable name `withApollo`

* Use the later version of graphql-let

* Only pages can be in pages

* Life improvements

* fix: .grpahql-let.yml point to the wrong document path

* Use a wider glob for less pitfalls
* Add a note about it in README.md
Co-authored-by: NLuis Alvarez D. <luis@zeit.co>

* add with-mobx-keystone-typescript example

* Use latest Next.js and removed gitignore

* Fixed my suggestions

* Enabled strict mode and simplified _app
Co-authored-by: NLuis Alvarez D. <luis@zeit.co>

* Tailwind example only run PurgeCSS in production

* Apply lint
Co-authored-by: NJoe Haddad <timer150@gmail.com>

* copy only the necessary files during stage 2 in multi-stage.

* update readme

* Remove redefinition of apolloClient

It seems that the definition of `apolloClient` on line 47 seems to be a intended to be defining the `apolloClient` defined in global scope. That re-declaration of the `apolloClient` variable is removed in favor of assigning the return of `initApolloClient()` to the globally defined `apolloClient`

* Rename the global apollo client to globalApolloClient

Closes #8935 #8934

* Remove next folder before build in with-react-intl

* Relax message id requirement in with-react-intl

* @formatjs/cli instead of babel-plugin-react-intl

* default-lang.js -> extract.js
Co-authored-by: NJoe Haddad <timer150@gmail.com>

* Fix relay URL

* Fix relay URL

* Fix relay URL

* update README to use create-next-app

* add links and update urls

* update BuckleScript package

* add node_modules to .gitignore

* fix the create-next-app command
Co-authored-by: NJJ Kasper <jj@jjsweb.site>

* copy only compiled files into electron build for with-electron-typescript

* updated npm deps for with-electron-typescript

* copy only compiled files into electron build for with-electron

* updated npm deps for with-electron
Co-authored-by: NJJ Kasper <jj@jjsweb.site>

* Update packages

* Update examples/with-typescript/package.json
Co-Authored-By: NJJ Kasper <jj@jjsweb.site>

* Run lint-fix
Co-authored-by: NJJ Kasper <jj@jjsweb.site>

* added AMP Google Analytics integration example

* added Amp custom element component w/ separate analytics component

* Update auth0 sample: bump dependencies and improve config management

* Fixed linter

* Fix symlink

With an update to sentry-testkit to depend on native node modules
this example no longer works in the browser. Sentry-testkit is made
for a node server not to work in the browser. However, with this
change we no longer require sentry-testkit in our setup for sentry.
Before this change with the update of sentry-testkit to 3.1 we were
encountering errors when trying to run the next.js local development
server because it was trying to load sentry-testkit in the browser.

Thank you to @ohana54 for his example found here https://github.com/wix/sentry-testkit/issues/43
this will now close this issue https://github.com/zeit/next.js/issues/9768
as well.

Reported at https://github.com/zeit/next.js/issues/9617

Use `AppTree` so that `withRouter` works correctly.

* Migrate to functional components

* Remove deprecated modules syntax

* Remove description

* Remove Counter

jest didn't include TS extensions by default, now it does.
Plus some minor adjustments.

* Update analyze-bundles example

* follow these updates:
  1. `server` and `browser` options
    * https://github.com/zeit/next-plugins/blob/9ecca7b492518464897ea866b4abcdc6214bf705/packages/next-bundle-analyzer/index.js
  2. "Deprecate next-bundle-analyzer"
    * https://github.com/zeit/next-plugins/commit/e453804d07f309d8b22e11930aa08a260f86108d#diff-5cea9b17189292d8fedc98eeda86bb0b
  3. "Move next-bundle-analyzer to Next.js repo"
    * https://github.com/zeit/next.js/commit/42cff0a09c4ae42016500b1797ae4f0bd8438e88#diff-4e57124572a8e05f52d373c300523f6a
    * "Remove options from bundle-analyzer"

* Support Windows in analyze bundles example

* Remove empty webpack config from analyze bundle example

* https://github.com/zeit/next.js/pull/9645/files/4943d844cc4bd73edfc58ae10d781def3de687af#r354844766

Looks like the directory name was missed after a copy/paste from another example.

* Using custom hook instead of `_app.js` to interface with
`socket.io-client`

- In with-next-sass example package
- Do not want example to use version 4.13.0 of node-sass

- For with-algolia-react-instantsearch example