* re-runs accepted modules

* propagates a hot update to closest accepted module

* propagates hot update to all inverse dependencies

* Add missing TODOs

* Separate Module Tests

* Fix incorrect link in with-passport example

Closes #11961

* hardcode link for with-passport README

* fix link
Co-Authored-By: NLuis Alvarez D. <luis@zeit.co>
Co-authored-by: NLuis Alvarez D. <luis@zeit.co>

* fix: with-mobx

* refactor: up link

* refactor: npm run prettier-fix

* refactor: server side render

* Updated store implementation and pages

* Updated readme
Co-authored-by: Nwangcheng <wangcheng@deepblueai.com>
Co-authored-by: NLuis Alvarez <luis@zeit.co>

* Add Fast Refresh Support

* Add Basic Acceptance Test

* Increase delay

* fix version

* Ignore test files

* Update packages/next/build/webpack/loaders/next-babel-loader.js

* Copy tests

* Redo test style

* drop directory

* fix compile

* fix remove function

* Update helpers

* Create React Refresh Utils

* Fix Linting

* Update Prettier Ignore

* fix rules

* refactor(next-client-pages-loader): allow toggling router HMR

* Turn on

* Toggle dev properly

* Fix Test Run Order

* Update HMR Client Runtime

* Increment event when building or different state

* Dismiss Old Type-Only Overlay

* Update packages/next/client/dev/error-overlay/hot-dev-client.js

* Enable "paths" support by default

* Enable NEXT_PUBLIC_ prefix exposing the variable globally

Part of #11106

This allows a page to be fully static (no runtime JavaScript) on a per-page basis.

The initial implementation does not disable JS in development mode as we need to figure out a way to inject CSS from CSS imports / CSS modules without executing the component JS. This restriction is somewhat similar to https://www.gatsbyjs.org/packages/gatsby-plugin-no-javascript/. All things considered that plugin only has a usage of 600 downloads per week though, hence why I've made this option unstable/experimental initially as I'd like to see adoption patterns for it first.

Having a built-in way to do this makes sense however as the people that do want to adopt this pattern are overriding Next.js internals currently and that'll break between versions.

Related issue: #5054 - Not adding `fixes` right now as this implementation needs more work. If anyone wants to work on this feel free to reach out on https://twitter.com/timneutkens

Co-authored-by: NJJ Kasper <jj@jjsweb.site>

* Disable PnP plugin in webpack 5
Co-Authored-By: NZack Jackson <zackary.l.jackson@gmail.com>

* Use full hashes for hot update names
Co-Authored-By: NZack Jackson <zackary.l.jackson@gmail.com>

* Disable autodll in webpack 5
Co-Authored-By: NZack Jackson <zackary.l.jackson@gmail.com>

* Disable HashedModuleIdsPlugin in webpack 5
Co-Authored-By: NZack Jackson <zackary.l.jackson@gmail.com>

* Use regexes for ignoreplugin as it only supports regexes in webpack 5
Co-Authored-By: NZack Jackson <zackary.l.jackson@gmail.com>

* webpack 4 supports resourceRegExp and contextRegExp
Co-Authored-By: NZack Jackson <zackary.l.jackson@gmail.com>

* Remove webpack 4 specific properties from the webpack 5 config
Co-Authored-By: NZack Jackson <zackary.l.jackson@gmail.com>

* Add library option for webpack 5 support
Co-Authored-By: NZack Jackson <zackary.l.jackson@gmail.com>

* Fix TypeScript Errors
Co-authored-by: NZack Jackson <zackary.l.jackson@gmail.com>
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>