* Added basic example for dynamic routing

* Added some basic docs for dynamic routing

* Added more docs for dynamic routing

* Used doctoc

* fixed lint issues

* Added useRouter to docs

* Removed getInitialProps examples that are only using router props

* Added useRouter to the navigation

* Small fix

* Updated to the latest dynamic routes implementation

* lint fix

* Update dynamic routing example

* Tweak dynamic routing documentation

* Make basic example basic again

* Adjust dynamic routes section

* Remove query param for dynamic routes example

* Remove old note

* Fix linting

* Updated with-zones example to Now V2

* Updated Zones docs

* Update packages/next/README.md
Co-Authored-By: NTim Neutkens <tim@timneutkens.nl>

* Add prerender PageConfig option

* Update PageConfig type

* Add inlining of data when pre-render is set and add tests

* Update types import

* Add check for props

* Rename prerender to experimentalPrerender for now

* Fixes serverless target in development

* Fix serverless build

* Fix serverless build

* Add manifest test

* Better output

* Fix manifest test

* Update snapshot

* Remove snapshots

Using runtime configuration can cause you to de-optimize entire classes of optimizations.
These optimizations could make your application an order of magnitude faster (i.e. prerendering).

The second line of this comment was removed in the previous commit due to the usage of process.browser.
This meant the comment was incomplete and confusing
https://github.com/zeit/next.js/commit/c03e94bebddff570e2181bf3b8c34adf0c704470#diff-a15b49cbb3a523d81a74e0fab7f08eb5

* Don't transpile styled-jsx in server mode

* Add test fo styled-jsx-module

* Add styled-jsx as dependency of next-server

* Add path to exportPathMap query missing message

* Path to Url

* Remove `withAmp` and do not expose `isInAmpMode`
This pull request removes the `withAmp` higher-order component in favor of the exported configuration object.
Retaining this backwards compatibility isn't worth the extra maintenance burden, given it hasn't been released for very long and the migration is ultra-simple.

I'm 👎 on retaining backwards compatibility just for the sake of it.

Migration example follows. I'm willing to write a codemod if reviewers feel it's necessary.

*Before*
```js
import { withAmp } from 'next/amp'

function Home() {
  return <h1>My AMP Page</h1>
}

export default withAmp(Home)
// or
export default withAmp(Home, { hybrid: true })
```

*After*
```js
export default function Home() {
  return <h1>My AMP Page</h1>
}

export const config = {
  amp: true,
  // or
  amp: 'hybrid',
}
```

* Fix { amp: 'hybrid' }
Co-Authored-By: NJJ Kasper <jj@jjsweb.site>

* added docs for disabling prefetch

* Update packages/next/README.md
Co-Authored-By: NJJ Kasper <jj@jjsweb.site>

* Expand automatic pre-rendering docs

* Apply suggestions from code review
Co-Authored-By: NLuis Fernando Alvarez D. <luis@zeit.co>

* Unflag Dynamic Routing

* Unflag Automatic Prerendering

* Ensure pages are lambdas for test

* Fix file check

* Fix tests

* oof

* Use lambda for document middleware test

This reverts commit 0fd7e685.

* Remove modules option from dynamic

* Remove old test

* Update helper function to invoke only on get

* Tests for body parsing

* Update api-utils.ts

* Update next-server.ts

* Update packages/next-server/server/next-server.ts
Co-Authored-By: NJJ Kasper <jj@jjsweb.site>

* Dynamic routes for API

* New structure

* Change next config

* Refactoring tests

* Fix newline

* Fix tests

* Remove dynamic from config

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

* Update index.test.js

* Clean up AMP logic

* Tweak AMP logic some more

* Rename hasAmpVersion to hybridAmp

* Asynchronously check for type errors

* Add TODO

* Fix webpack invalidation

* Show TypeScript error in dev client

* Updating hapijs package name

Hapi was moved to a new module under the name @hapijs/hapi.

Right now installing just as hapi is giving you this warning:

```bash
npm WARN deprecated hapi@18.1.0: This module has moved and is now available at @hapi/hapi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
```
This change does not affect the integration with next and it continues to work great.

* Update package.json