Can't import the named export 'BridgeProxy' from non EcmaScript module (only default export is available) #6906
Unanswered
VishwasDevtech
asked this question in
Help
Replies: 2 comments 2 replies
-
@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 In similar ticket discussion you'll see people mentioning a needed webpack module rule:
But this isn't gonna be the fix for me. Sadly we are in an old CRA / react-scripts situation. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @VishwasDevtech @shmup |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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'],
});
};
return (
Sign in via Microsoft
);
};
export default MierosoftLoginButton;
`
Beta Was this translation helpful? Give feedback.
All reactions