Open
Conversation
ingoncalves
approved these changes
Feb 6, 2026
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
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.
React 17 to 18 Migration Summary
Successfully migrated the swagger-ui repository from React 17 to React 18, implementing all necessary changes to support React 18's new concurrent rendering features and updated APIs.
Changes Implemented
Dependency Updates:
Code Updates:
ReactDOM.render()toReactDOM.createRoot()API in the core rendering logiccreateRootfromreact-dom/clientas required by React 18Compatibility Notes
All existing lifecycle methods in the codebase already use the
UNSAFE_prefix, making them compatible with React 18's StrictMode. React 18's automatic batching feature is enabled by default and will improve performance for state updates outside of React event handlers. No hydration changes were required as the application does not use server-side rendering. The migration maintains full backward compatibility while enabling access to React 18's new concurrent features likestartTransitionanduseDeferredValueif needed in the future.