Comprehensive Refactoring to Fix Fast Refresh Issues in Vite #525
Conversation
This file contains 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.
In this PR, we address the critical Fast Refresh issues that arose following our migration from CRA to Vite. The changes are targeted at resolving "[vite] (client) hmr invalidate" errors and ensuring that our development environment leverages Vite's capabilities efficiently.
Key Changes:
CredentialsContext,CredentialParserContext,OpenID4VCIContext,OpenID4VPContext,SessionContext, andStatusContextto TypeScript, optimizing them for better integration with Vite’s module reloading.CredentialsContextProviderandStatusContextProviderfor clarity and consistency. Changed.tsxfile extensions to.tsinsrc/lib, reflecting non-JSX content.extractPresentationslogic fromhistoryDetailsto streamline component responsibilities and improve module handling.