From c6364c34804c7d8d938f118023ca6330b9f4d1fd Mon Sep 17 00:00:00 2001 From: Kai Vandivier <49666798+KaiVandivier@users.noreply.github.com> Date: Sat, 2 Nov 2024 14:53:31 +0100 Subject: [PATCH] docs: last suggestions Co-authored-by: Rene Pot --- docs/migration/v12.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/migration/v12.md b/docs/migration/v12.md index ffc240bf..9611e0e4 100644 --- a/docs/migration/v12.md +++ b/docs/migration/v12.md @@ -322,11 +322,11 @@ Here are some edge cases that were encountered when upgrading some apps with the ## Full list of breaking changes and deprecations -Larger items are mentioned above, but these lists are included for completeness. +The most likely and impactful breaking changes have been described in detail above. However this doesn't cover all the breaking changes and deprecations introduced in this upgrade. Below is the exhausted list. ### Breaking changes -1. Node 18 || 20+ is required +1. Node 18 or Node 20+ is required. Node 19 is not supported. 2. JSX in files without .jsx or .tsx extensions is not supported by default 3. React 18: Most significant testing changes are described above; the rest can be read about in the React [migration guide](https://react.dev/blog/2022/03/08/react-18-upgrade-guide) 4. Flow types won't work, although this is a motivator for extensible config