* add rosetta example
* add comment
* add example for ssr
* add debug example, rerender when i18n keys are added
* output active locale, fix interpolation, fix cases for SSR and CSR
* add useful comments
* address pr issues
* update name in readme
* improve wording
* rename folder
* fix prop typo, add redirects
* load specific i18n json file in getStatisProps
Dashboard dont use any ssr technique
* use ext
* improve example
* Updated example
Co-authored-by: Luis Alvarez <luis@zeit.co>
* update postcss.config.js to fix warnings
Return empty array if the condition is not met to avoid a null/undefined PostCSS plugin.
Related PR: https://github.com/zeit/next.js/pull/11366
* style: correct linting error
* 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: Luis Alvarez D. <luis@zeit.co>
Co-authored-by: Luis 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: wangcheng <wangcheng@deepblueai.com>
Co-authored-by: Luis Alvarez <luis@zeit.co>
* 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
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
* Disable PnP plugin in webpack 5
Co-Authored-By: Zack Jackson <zackary.l.jackson@gmail.com>
* Use full hashes for hot update names
Co-Authored-By: Zack Jackson <zackary.l.jackson@gmail.com>
* Disable autodll in webpack 5
Co-Authored-By: Zack Jackson <zackary.l.jackson@gmail.com>
* Disable HashedModuleIdsPlugin in webpack 5
Co-Authored-By: Zack Jackson <zackary.l.jackson@gmail.com>
* Use regexes for ignoreplugin as it only supports regexes in webpack 5
Co-Authored-By: Zack Jackson <zackary.l.jackson@gmail.com>
* webpack 4 supports resourceRegExp and contextRegExp
Co-Authored-By: Zack Jackson <zackary.l.jackson@gmail.com>
* Remove webpack 4 specific properties from the webpack 5 config
Co-Authored-By: Zack Jackson <zackary.l.jackson@gmail.com>
* Add library option for webpack 5 support
Co-Authored-By: Zack Jackson <zackary.l.jackson@gmail.com>
* Fix TypeScript Errors
Co-authored-by: Zack Jackson <zackary.l.jackson@gmail.com>
Co-authored-by: Joe Haddad <joe.haddad@zeit.co>
