rsnext/test/development
Hannes Bornö 2313ee093a
Display full refresh warning even when error has occurred (#37425)
If you end up in a state where an error happened and you also should be warned about a full refresh  - you get stuck. The full refresh is blocked by the warning but the error is shown instead.

Tests didn't catch this because the refresh warning never showed in `__NEXT_TEST_MODE`.

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`
2022-06-19 00:00:14 +00:00
..
acceptance Display full refresh warning even when error has occurred (#37425) 2022-06-19 00:00:14 +00:00
basic Display full refresh warning even when error has occurred (#37425) 2022-06-19 00:00:14 +00:00
basic-basepath Display full refresh warning even when error has occurred (#37425) 2022-06-19 00:00:14 +00:00
client-dev-overlay Allowing hiding the ReactDevOverlay (#37417) 2022-06-06 14:21:53 -04:00
dotenv-default-expansion feat: allow dotenv default expansion (#34765) 2022-03-03 16:52:20 +00:00
gssp-notfound Ensure we don't poll page in development when notFound: true is returned (#34352) 2022-02-16 18:53:48 +00:00
middleware-warnings feat(middleware)!: forbids middleware response body (#36835) 2022-05-19 22:02:20 +00:00
watch-config-file improve getStaticProps error message (#34287) 2022-05-22 16:50:21 -05:00
webpack-issuer-deprecation-warning fix(next): use moduleGraph.getIssuer to avoid deprecation warning (#36329) (#36330) 2022-04-21 14:14:03 +00:00