Chore/update to react 19

[arjenbloemsma]

Please note that this is a "copy" of PR #7467 which got accidentally closed while doing an update to resolve conflicts

React 19 stable has been released on December 5th (see announcement). This PR updates the react packages to version 19 and also sets the peerDependecies to reflect this.

This change will allow msal-react to be used in projects that use react 19 and enables existing projects that use react and msal-react to upgrade to react 19.

All test succeed:

See issue #7455

[iampoul]

What needs to be done for this to go out of draft.

[SM-OliLegg]

Suggested change

	"@types/react": "^19.0.01",
	"@types/react": "^19.0.10",

[antonakospanos]

@arjenbloemsma we would also like to upgrade our stack to React 19 and we are stuck because of this. Are you ok accepting the suggestion so that we include this in the next release?

[JackMorganNZ]

Similar to others here, our path to React 19 is blocked due to this package. @arjenbloemsma Is this okay to be marked as ready? Is there anything we can do to assist?

[LeonFedotov]

@tnorling do you mind taking a look please?

[samuelms1]

Really excited for the React 19 support. It's the last package holding up my company's upgrade. Super appreciate @arjenbloemsma opening the PR and others that contribute to the repo.

[julesblancphin]

Any updates on this? @tnorling @jo-arroyo @peterzenz, the community has been eagerly waiting for react 19 support for 4 months now. Thanks.

[binu1-pararath-c5i-ai]

Is this held up because of genuine reasons? Will it be a good idea if someone confident enough shall fork msal-react and msal-browser and break this seemingly indefinite wait?

[samuelms1]

Is this held up because of genuine reasons? Will it be a good idea if someone confident enough shall fork msal-react and msal-browser and break this seemingly indefinite wait?

Not sure about why it's being held up but as suggested by some others, simply applying overrides works just fine. I've been using MSAL with React 19 for a couple weeks with no issues. Unrelated, but I had to do the same thing with swagger-ui-react too.

I really appreciate the folks that keep these libraries nice. They're doing a lot.

Here's the post that I followed and it worked perfectly:

I've managed to upgrade to react@19 by adding "overrides" in package.json. Haven't run into any issues since January

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

See #7577 (comment)

[tnorling]

Closing in favor of #7735