Can't import the named export 'BridgeProxy' from non EcmaScript module (only default export is available)

[VishwasDevtech]

I'm getting this compile error in my React-typescript code:
Can't import the named export 'BridgeProxy' from non EcmaScript module (only default export is available), in the below node_modules file:
./node_modules/@azure/msal-browser/dist/operatingcontext/TeamsAppOperatingContext.mjs
Can anyone please help me with this issue?
This is my code:
`import React, { useState } from 'react';
import * as MSAL from '@azure/msal-browser';
import MicrosoftLogo from '../../assets/logos/microsoft.png';
import { Email } from 'components/styled-components/common';
import { loginRequest, msalConfig } from '../../util/msAuthConfig';

const MierosoftLoginButton = () => {
const msalInstance = new MSAL.PublicClientApplication(msalConfig);
const [account, setAccount] = useState(null);
const login = async () => {
try {
await msalInstance.loginPopup({
scopes: ['openid', 'profile', 'User.Read'],
});

  const account = msalInstance.getActiveAccount();
  if (account) {
    setAccount(account);
    console.log('Hello ', account);
  }
} catch (error) {
  console.log(error);
}

};
return (


Sign in via Microsoft

);
};

export default MierosoftLoginButton;
`

[shmup]

@VishwasDevtech I'll let you know what the fix is for me. Recently started work on introducing msal-browser into a production app that could use some dependency updates.. and so, our first experience with .mjs imports ala @azure/msal-browser

In similar ticket discussion you'll see people mentioning a needed webpack module rule:

test: /\.(mjs)$/,
exclude: /node_modules/,
use: ['javascript/auto'],

But this isn't gonna be the fix for me. Sadly we are in an old CRA / react-scripts situation.

[Sudharsan7777]

Hi @VishwasDevtech @shmup
did you find the solution? we are in the same situation

[shmup]

@Sudharsan7777 Not yet, I'm going to talk with the team next week. I'll let ya know what we go with, but it won't be an easy path regardless. I have a hunch it'll come down to upgrading a bunch of dependencies by initially updating CRA, and working through compiler errors.