`@azure/msal-react` v3 pushed to `latest` tag

[h3rmanj]

Core Library

MSAL.js (@azure/msal-browser)

Core Library Version

latest

Wrapper Library

MSAL React (@azure/msal-react)

Wrapper Library Version

latest

Public or Confidential Client?

Public

Description

msal-react@v3 has been pushed to the latest tag on npm.
https://www.npmjs.com/package/@azure/msal-react?activeTab=versions

When running install, i get this output:

npm install @azure/msal-browser @azure/msal-react
# msal-browser@4 & msal-react@3 is installed

npm install @azure/msal-browser@latest @azure/msal-react@latest
# errors because it tries to resolve msal-browser@5, but msal-react@3 wants msal-browser@4

npm install @azure/msal-browser@5 @azure/msal-react@5
# works, but I shouldn't need to explicitly request v5 of both libraries

Error Message

No response

MSAL Logs

No response

Network Trace (Preferrably Fiddler)

• Sent
• Pending

MSAL Configuration

{}

Relevant Code Snippets

`npm install @azure/msal-browser @azure/msal-react`

Reproduction Steps

npm install @azure/msal-browser @azure/msal-react

Expected Behavior

Version 5 is installed.

Identity Provider

Entra ID (formerly Azure AD) / MSA

Browsers Affected (Select all that apply)

Other

Regression

No response

[revov]

Problem here is developers installing the standard @azure/msal-browser @azure/msal-react at the moment will run into build errors as they will end up with incompatible versions and will wonder why they are getting an error just following getting started guides.

[lalimasharda]

Hey @h3rmanj, we just updated the latest tags in npm to point to the correct latest versions. This should be fixed now! Can you please try again and let me know.

[h3rmanj]

Thanks @lalimasharda! Looks correct on npmjs.com, and installs works as expected now.

But I think the most important thing here is that you've fixed the pipeline/release script that allowed this to happen in the first place!

[lalimasharda]

Thanks for confirming, closing this issue.