@azure/msal-angular v3.0.0-alpha.0

[hectormmg]

3.0.0-alpha.0

Tue, 02 May 2023 23:14:26 GMT

Major changes

• Update msal-angular to Angular 15 (joarroyo@microsoft.com)
• Rebase dev onto v3 Rebase dev onto v3 #5843 (kshabelko@microsoft.com)
• Bump @azure/msal-browser to v3.0.0 (beachball)

Patches

• Fix package-lock.json Move node clients from msal-common to msal-node #5788 (kshabelko@microsoft.com)

[sandrooco]

It's great to finally see (alpha) Angular 15 support. Thank you. A few inputs:

• There were multiple attempts in the community to provide PRs for a long time, this isn't mentioned anywhere. I fear this will drive down the community's support, at least for me personally. I probably won't try again to support the project.
• Angular 15 support came after Angular 16 itself was released - that's below any library's standards in my book

I'm aware that things sometimes "are just not that simple" in bigger companies. This case was quite bad though...

[jerone]

100% agree.

I'm aware that things sometimes "are just not that simple" in bigger companies. This case was quite bad though...

Specially, as you mentioned, multiple working attempts where provided with support for Angular 15 and Ivy.

[NateRadebaugh]

The followup question is: "When will Angular 16 support be ready?"

[NateRadebaugh]

To answer my own question, the 3.0 alpha does work with angular 16.

This PR has an example app for angular 16: #5944

Ultimately, the following is the minimum to support angular 16:

"@azure/msal-angular": "^3.0.0-alpha.0",
"@azure/msal-browser": "^3.0.0-alpha.0",

[kyubisation]

@sandrooco Thanks for bringing this up 👍
As someone who also tried to contribute part of this feature and also was in direct contact with the responsible Azure AD team and provided feedback (as early as 2021), this is simply abysmal.
This instills zero confidence in this library and prevents me, as a product owner for web frontends in my company, to recommend it.