Add react 19 to peer deps

[lucas-garrido]

Core Library

MSAL.js (@azure/msal-browser)

Wrapper Library

MSAL React (@azure/msal-react)

Public or Confidential Client?

Public

Description

React 19 is now stable could you update the peer dependencies please ?

[arjenbloemsma]

I totally agree with @lucas-garrido. This is currently blocking our app from being upgraded.

[arjenbloemsma]

Created a PR to address this: #7467

[ritwickg]

This complete blocker for any react 19 upgrades with SSO

[arjenbloemsma]

Just mentioned this in the PR, but will also mention it here:

To unblock my project, I've published a npm package of the msal-react fork. This allows us to keep moving forward and use react 19 in dev and test while the official package has not yet been released. Once the new version of official msal-react is released we can simply change back to that package, rebuild and move on.

For those interested in following a similar approach; https://www.npmjs.com/package/@arjenbloemsma/msal-react

[bdbvb]

Another temporary workaround, from the consuming package.json file:

"overrides": {
    "@azure/msal-react": {
        "react": "^16.8.0 || ^17 || ^18 || ^19"
    }
}

[3pleFly]

waiting for this..

[marvinjaworski]

Please prefer this problem, I have already tested it manually with the described fix and it seems to work very well. We are urgently waiting for the update to use react 19.

[julesblancphin]

Any updates on this?

[aclebson-sage]

Any updates on this?

I resolved this issue by updating to the versions: ├── @azure/[email protected] ├── @azure/[email protected]

[bdbvb]

Any updates on this?

I resolved this issue by updating to the versions: ├── @azure/[email protected] ├── @azure/[email protected]

FYI, this would be a downgrade/workaround, not really a resolution.

[aclebson-sage]

Any updates on this?

I resolved this issue by updating to the versions: ├── @azure/[email protected] ├── @azure/[email protected]

FYI, this would be a downgrade/workaround, not really a resolution.

for this specific case, it was the solution since version constraints on other React packages

[greatzambino]

I also am blocked by this

[jansonjc]

Another temporary workaround, from the consuming package.json file:

"overrides": {
    "@azure/msal-react": {
        "react": "^16.8.0 || ^17 || ^18 || ^19"
    }
}

Looks like a reasonable workaround. Did anyone get into any issues with it?

[greatzambino]

It seems to be working well on my end

[User6531]

Another temporary workaround, from the consuming package.json file:

"overrides": {
    "@azure/msal-react": {
        "react": "^16.8.0 || ^17 || ^18 || ^19"
    }
}

Looks like a reasonable workaround. Did anyone get into any issues with it?

A week in production, and no issues so far.

[tibble49]

Is there an ETA on this?

[benc-uk]

Guys come on, this is not cool. It's been ~5 months and no fix? If you were a one man team, I'd get it, but you ain't

[MarianoVeloso]

I'm not going to be sympathetic or anything like that. People pay to use Azure AD. RCs for React 19 have been available practically since last year, and it's been 5 months since React released version 19. It's disrespectful.

[julesblancphin]

@sameerag @peterzenz @jo-arroyo @tnorling please advise the community, there has been 0 communication for months now. As @MarianoVeloso mentioned this is a paid product and the lack of response and support is unprofessional.

[julesblancphin]

For anyone curious, there's been an update here https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/7722#issuecomment-2836079014

Essentially React 19 support is not a priority for the MS team and there's some additional work required for the PRs that have been opened.

[timtucker-dte]

I'm not going to be sympathetic or anything like that. People pay to use Azure AD. RCs for React 19 have been available practically since last year, and it's been 5 months since React released version 19. It's disrespectful.

There seems to be a broader issue across multiple MS projects / departments in supporting updated dependency / runtime versions.

A reasonable expectation from customers:

• Dependency releases a preview version
• Developers of components that build upon it (like MS) start making sure that their components are compatible
• Final version of dependency is released (~6 months after preview)
• Component developers release a version that supports the new dependency (~1 month after release)

What we see instead:

• Dependency releases a preview version
• MS is still playing catchup finalizing support for the previous version
• Final version of dependency is released
• Next preview version of the dependency is released
• MS releases a version that supports the new dependency (~6-12 months after release)

When combined with MS's support policy for dependencies, the net effect is that the N-2 version is often deprecated or out of support before N is supported.