Cannot find module '@azure/msal-angular' or its corresponding type declarations. Angular 16

[theviveik1]

Core Library

MSAL.js (@azure/msal-browser)

Core Library Version

3.0.0

Wrapper Library

MSAL Angular (@azure/msal-angular)

Wrapper Library Version

3.0.0

Public or Confidential Client?

Public

Description

Cannot find module '@azure/msal-angular' or its corresponding type declarations.

The module '@azure/msal-angular' or its corresponding type declarations could not be located. Despite having installed @azure/[email protected], I'm encountering difficulties in utilizing the library. Refer to the image below for more context. It's important to note that I'm utilizing the library with Angular 16, having previously used version 3.0.0-beta.1, which functioned as anticipated.

Error Message

No response

Msal Logs

No response

MSAL Configuration

import {
  MsalBroadcastService,
  MsalGuard,
  MsalInterceptor,
  MsalModule,
  MsalRedirectComponent,
  MsalService,
  MSAL_GUARD_CONFIG,
  MSAL_INSTANCE,
  MSAL_INTERCEPTOR_CONFIG
} from '@azure/msal-angular';

Relevant Code Snippets

import { MsalGuard } from '@azure/msal-angular';

Reproduction Steps

1. download any angular 16 project
2. configured whatever is required for msal
3. then run npm install @azure/[email protected] @azure/[email protected]
4. npm start

Expected Behavior

Application should run.. but receiving below error

Identity Provider

Azure AD / MSA

Browsers Affected (Select all that apply)

Chrome, Internet Explorer

Regression

@azure/[email protected] @azure/[email protected]

Source

External (Customer)

[solita-markuspulkkinen]

content of node_modules/@azure/msal-angular seems to have just src and no dist || other build results

[hansakaRightS]

we are having the same issue.check here #6310

[theviveik1]

Please link this bug with #6310, so that i can follow the same whatever the status change would notified me.

[jo-arroyo]

@theviveik1 As others have stated above, there has been an error in our release process for msal-angular, and we are currently working on a fix. Please follow #6310, where the issue was first raised, and where updates will be posted.

Closing as duplicate of #6310.