Additional msal-react v5 migration details#8386
Merged
Conversation
peterzenz
previously approved these changes
Mar 6, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the migration documentation for MSAL Browser (v4-migration.md) and MSAL React (migration-guide-v4-v5.md) to clarify the upgrade path to v5, providing explicit code examples and compatibility notes for developers.
Changes:
- Added migration path guidance (v1/v2/v3 → v5), COOP redirect bridge setup instructions, React 18 compatibility notes, and an
InteractionStatuscode migration example to the msal-react v4-v5 migration guide. - Added a
LOGIN_SUCCESSpayload type migration section with before/after TypeScript code samples to the msal-browser v4-migration guide.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
lib/msal-react/docs/migration-guide-v4-v5.md |
Adds migration paths, COOP bridge section, React 18 workaround note, and InteractionStatus code migration example |
lib/msal-browser/docs/v4-migration.md |
Adds LOGIN_SUCCESS payload type migration section with before/after TypeScript code examples |
lalimasharda
previously approved these changes
Mar 6, 2026
Contributor
…8387) The migration guide stated "React 19 or greater" but the actual peer dependency is `"react": "^19.2.1"`, meaning React 19.0.x and 19.1.x do **not** satisfy the constraint. ## Changes - **`lib/msal-react/docs/migration-guide-v4-v5.md`**: Replace both occurrences of "React 19 or greater" / "19+" with "React 19.2.1 or greater" to match the declared peer dependency. <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: tnorling <5307810+tnorling@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
jennyf19
approved these changes
Mar 6, 2026
peterzenz
approved these changes
Mar 7, 2026
jmprieur
reviewed
Mar 7, 2026
|
|
||
| ## COOP redirect bridge setup (required) | ||
|
|
||
| MSAL Browser v5 requires a dedicated redirect page/bridge for authentication flows. |
Collaborator
There was a problem hiding this comment.
may be worth double-checking for scope/wording so it doesn’t read more universally than intended?
Collaborator
Author
There was a problem hiding this comment.
This is a universal requirement
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.
This pull request updates the migration documentation for both MSAL Browser and MSAL React to clarify the required steps for upgrading to v5, including payload type changes, migration paths, and compatibility notes. The changes provide explicit migration examples and highlight new requirements and breaking changes.
MSAL React v5 Migration Guidance and Compatibility:
MSAL Browser v5 Event Handling Changes:
LOGIN_SUCCESSpayload type, including before/after TypeScript code samples to illustrate the migration from casting toAuthenticationResultto usingAccountInfo.InteractionStatus and Event Consolidation:
InteractionStatusvalues and provided a migration example for simplifying in-progress status checks in React apps.These updates ensure developers have clear, actionable steps for migrating to the latest major versions and handling breaking changes in event payloads and interaction status.