Upgrade React to v16 in XUI#201
Merged
pavelhoral merged 2 commits intoWrenSecurity:mainfrom Jun 13, 2025
Merged
Conversation
krausvo1
force-pushed
the
react_16_upgrade
branch
from
5f3fba2 to
49cb857
Compare
Contributor
Author
|
I have dropped dependencies "react-bootstrap-table-next" and "react-bootstrap-table2-paginator" that I included accidentally. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR upgrades React and React-related dependencies to versions compatible with React 16 in XUI. React 16 is used since we upgraded wrensec-ui to 23.2.0.
Most of the required changes are related to PropTypes being separated to dedicated
prop-typeslibrary. Apart from that and upgrades of other React-related dependencies, another big change is refactoring of Sessions page, where new component for asynchronous select input was added as a wrapper forreact-select'sAsynccomponent.I have tested all pages where React components are used and haven't encountered any issues after the upgrade.