Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[@azure/identity] Uncaught Error: EnvironmentCredential is not supported in the browser.
See original GitHub issuePackage/Version: @azure/identity@1.2.1
Is your feature request related to a problem? Please describe.
When I attempt to use @azure/identity in the browser I get this error:
Uncaught Error: EnvironmentCredential is not supported in the browser.
Describe the solution you’d like I would like this use case to actually work. We inject env vars into the build using webpack. Its a convenient way to inject various bits in test scenarios. In our case we make a “fake” Azure Portal wrapper around our project that injects these variables into the page. Webpack will handle the injection for us, but it won’t work when this case is explicitly rejected by the identity SDK.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think I’m fine with manually plumbing environment variables. It might be convenient for tests to have this auto-picked up but it feels like such a risky thing to enable/have built in support for. You really should think hard using env vars in the browser.
@southpolesteve For the specific scenario you mention, would you be willing to consider writing a custom TokenCredential that does what you want?