* Add better hash URL support.
1. Add scrolling to given id related to hash
2. Hash changes won't trigger getInitialProps

* Add some comments.

* Fix tests.

* Add some test cases.

https://greenkeeper.io/

Earlier it wait until the JSON page is fetched.
But that's wrong and it affects when using libs like NProgress.

With the on-demand-entires, this makes no sense.

* Move on-demand-entries-ping to _next namespace

* Ignore .next from watching

* Make sure to invalidate only once before webpack complete the build.

* Increase the touch timeout to 1 sec.

* Add benchmarks for server rendering

* Remove bench from flyfile

Bring back https://github.com/zeit/next.js/commit/1b9e8771ec569def1773040b68f404c2cbc9484e with a check for the prefetch serviceworker + if it is supported by the browser

https://greenkeeper.io/

https://greenkeeper.io/

* Add a plan for dynamic entry middleware.

* Use dynamic pages middleware to load pages in dev.

* Add the first version of middleware but not tested.

* Integrated.

* Disable prefetching in development.
Otherwise it'll discard the use of dynamic-entries.

* Build custom document and error always.

* Refactor code base.

* Change branding as on-demand entries.

* Fix tests.

* Add a client side pinger for on-demand-entries.

* Dispose inactive entries.

* Add proper logs.

* Update grammer changes.

* Add integration tests for ondemand entries.

* Improve ondemand entry disposing logic.

* Try to improve testing.

*  Make sure entries are not getting disposed in basic integration tests.

* Resolve conflicts.

* Fix tests.

* Fix issue when running Router.onRouteChangeComplete

* Simplify state management.

* Make sure we don't dispose the last active page.

* Reload invalid pages detected with the client side ping.

* Improve the pinger code.

* Touch the first page to speed up the future rebuild times.

* Add Websockets based pinger.

* Revert "Add Websockets based pinger."

This reverts commit f706a49a3d886d0231259b7a1fded750ced2e48f.

* Do not send requests per every route change.

* Make sure we are completing the middleware request always.

* Make sure test pages are prebuilt.

https://greenkeeper.io/

* Remove traces of glamor

As talked about with @rauchg. Glamor takes up around 60KB of the bundle (pre-gzip). Since styled-jsx is the way to go now and we support adding glamor by the user we should remove it as dependency cause it is bundled even when not used.

Added rehydration to the example, since we did that in our code.

There is only one thing I'm not sure about and want to discuss:
what should we do with next/css. Right now I added a throw for when it is imported. I'm not sure if we should do that / some other way to notify the user it has been removed. The reasoning behind the throw is that when we would do a console.warn the user would see 'css.default.<X>' not found because we don't have the glamor dependency anymore.

* Update yarn.lock

* Remove test for styles

This reverts commit 756a32ae.

See https://github.com/zeit/next.js/pull/1278#issuecomment-282528628

https://greenkeeper.io/

* Add example app with React Intl

Fixes #1022

* Update examples/with-react-intl/package.json to be consistent

https://greenkeeper.io/

* Fix relative module aliases for Windows

* Update regular expressions to use `path.sep` instead of `[\\/]`

* Make the minimal changes possible.

* Add message for missing peerDependencies

* Remove exit

* Use console.warn

https://greenkeeper.io/

* Run tests in Travis.

* Update deps and config.

* Update jest config.

* Disable a test temp.

* Increase the timeout.

https://greenkeeper.io/

Check currentTarget is 'A', not target. This is important when an anchor tag wraps another dom node.

https://greenkeeper.io/

https://greenkeeper.io/

Tried to pull & run this example, it failed, complaining about missing react & react-dom dependencies