msal-angular@1.0.0-beta.5 imports fail

[jarodsmk]

Library

• msal@1.3.0-beta.1
• @azure/msal-angular@1.0.0-beta.5

Framework

Angular@8.2.3

Description

When bumping msal-angular to 1.0.0-beta.5, BroadcastService and MsalService can no longer be imported.

The path @azure/msal-angular doesn't resolve to a module in node_modules.

Security

None

Regression

Yes this worked before, when reverting to @azure/msal-angular@1.0.0-beta.4 it works fine.

Configuration

// Provide configuration values here.
// For Azure B2C issues, please include your policies.

config: {
      auth: {
        clientId: 'XXX',
        authority:
          'XXX',
        validateAuthority: true,
        redirectUri: 'http://localhost:4200/auth-callback',
        postLogoutRedirectUri: 'http://localhost:4200/',
        navigateToLoginRequestUrl: true,
      },
      cache: {
        cacheLocation: 'localStorage',
        storeAuthStateInCookie: false, // set to true for IE 11
      },
    },
    angularConfig: {
      popUp: false,
      consentScopes: ['openid', 'profile', 'email'],
      protectedResourceMap: [
        ['https://localhost:5001', ['openid', 'profile', 'email']],
      ],
      extraQueryParameters: {},
    },

Reproduction steps

1. From a 1.0.0-beta release, bump it to 1.0.0-beta.5
2. The imports previously set as per the Angular Sample App examples should fail because the module cannot be reconciled.

Expected behavior

The imports should still work after the version change.

Browsers

Not browser specific

[jasonnutter]

@jarodsmk I'm having trouble reproducing this with the Angular 8 sample. Installed beta 5 from npm, and everything looks good. The artifact on npm looks good as well, seems like everything is there. Are all the files there inside node_modules/@azure/msal-angular?

[jasonnutter]

Closing due to inactivity and the inability to reproduce the issue, please let us know if this is still an issue.