The links for `emotion` and `emotion-server` in the emotion example's readme were 404ing.

After going to Emotion's repo, I noticed [the packages were renamed](https://github.com/emotion-js/emotion/issues/1635).

This PR updates the links: `emotion` -> `emotion/css` and `emotion-server` -> `emotion/server`

Where it reads "We start of..." should be "We start off..".

Co-authored-by: NTim Neutkens <timneutkens@me.com>

Co-authored-by: NDale Bustad <dale@divmain.com>

@timneutkens this adds a trace capturing script alongside the other tracing sundry.  This will be utilized by the performance automation.  Additionally, its nice to have an option other than running the ZipKin JAR to get at the raw data.

Co-authored-by: NmAAdhaTTah <jamesorodig@gmail.com>

This updates to only create locale domain links if the current hostname is a locale domain to prevent making links unvisitable in development and preview environments where the configured locale domains don't point to the current build. 

Closes: https://github.com/vercel/next.js/issues/21211
Closes: https://github.com/vercel/next.js/issues/22011

This adds ncc'ing the AMP optimizer package to speed up install times and cache the runtime. 

Closes: https://github.com/vercel/next.js/issues/20404

This ensures we pass the error up to the top-level when in minimal mode

Makes sure `yarn trace build` works.

Co-authored-by: NLee Robinson <me@leerob.io>

This PR updates the React packages version in the example with Tailwind.
Thus solving the new version notice when starting the project in dev.

Notice screenshot: 📸 
![image](https://user-images.githubusercontent.com/25041169/107084102-5bc0f780-67d5-11eb-82bb-b9ea2682ec5c.png)

Now with the updated version:📸 
![image](https://user-images.githubusercontent.com/25041169/107084154-71ceb800-67d5-11eb-95c9-54ea534145dd.png)

Missed this then changing the modules array to rely on `module.id`

This reverts commit 9a3a0da3.

I met following warning message after invoking create-next-app for ` example/with-typescript-eslint-jest `:

```
 % yarn dev
yarn run v1.22.10
$ next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
warn  - React 17.0.1 or newer will be required to leverage all of the upcoming features in Next.js 11. Read more: https://err.sh/next.js/react-version
event - compiled successfully
```

I have followed the instructions in the link, and this patch is. Please merge this.

Thank you for reading.

Tested against some smaller apps. Will have a high impact for larger apps.

This implements the compatibility require hook as per https://github.com/vercel/next.js/issues/21789.

The hook is applied at the point of webpack initialization. In addition the separate packages are exposed for the various webpack subrequires.

The test then ensures instance equality for the basic require hook from the next.js config file.

I suspect this might have bad interactions with Yarn Pnp support, but maybe we will be lucky.

Adds versioning for the stats output

Address one of the bullet points from https://github.com/vercel/next.js/issues/15225 to remove unused dependencies on `dotenv` now that it's supported by default in Next.js.

The top-level script has always been `dev` so this makes the package scripts consistent

This adds a simple typing definition to the Webpack ncc output.

Fixes https://github.com/vercel/next.js/issues/21390.