Closed MMMalik closed 2 years ago
This is ready for review.
One more considration to be taken into account: React 18 drops support for IE11 :see_no_evil:. So if we enable support for React 18 exclusively, then we also basically drop support for IE11 in React integration.
There are still alternative routes we can take. For instance, we can enable support for React from 16.8.x to 18.x AND loosen our testing policies:
This way we could cover with tests all versions our source code would work on and unlock official support for React 16.8 to 18.x via peerDependencies
:
"peerDependencies": {
"ckeditor4": "^4.19.0",
"react": "^16.8 || ^17 || ^18"
},
This is ready for another round of review.
Few changes were introduced:
import type ...
).react-dom/client
API.
This PR officially enables support for React 18. The following work has been done:
peerDependencies
field inpackage.json
.chalk
which relies on ESM since v5).Closes #284.