chore(react): use new JSX transformations and remove react-axe #1129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/main
Related to #1110
Related to #482
Description of the change:
react
.react-axe
in dev environment.Motivation for the change:
For references about namespaced/named imports and JSX transformation:
https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
For
react-axe
, there is a hiccup about the requirement of default imports for React. I removed it here since we are not using in dev environment, at least until #947. There, perhaps we can explore axe cli (https://github.com/dequelabs/axe-core-npm/blob/develop/packages/cli/README.md).This is one of the first steps to upgrade to React 18 and PF 5.
References
https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
https://devblogs.microsoft.com/typescript/announcing-typescript-4-1/#jsx-factories