azure-sdk-for-js: Circular dependency
@azure/identity is throwing a Circular dependency warning. I have placed the text warning and picture.
I am importing @azure libraries as:
import * as azureIdentity from '@azure/identity';
import * as appConfig from '@azure/app-configuration';
Warning:
Circular dependency: node_modules\@azure\identity\node_modules\@opentelemetry\api\build\src\index.js -> node_modules\@azure\inode_modules\@opentelemetry\api\build\src\internal\global-utils.js -> node_modules\@azure\identity\node_modules\@opentelemetr Circular dependency: node_modules\@azure\identity\node_modules\@opentelemetry\api\build\src\index.js -> node_modules\@azure\inode_modules\@opentelemetry\api\build\src\internal\global-utils.js -> C:\Users\JBlanco\Documents\MFE - Product\node_modules\\@azure\identity\node_modules\@opentelemetry\api\build\src\index.js Circular dependency: node_modules\@azure\core-http\node_modules\@opentelemetry\api\build\src\index.js -> node_modules\@azure\tp\node_modules\@opentelemetry\api\build\src\internal\global-utils.js -> node_modules\@azure\core-http\node_modules\@opentele Circular dependency: node_modules\@azure\core-http\node_modules\@opentelemetry\api\build\src\index.js -> node_modules\@azure\tp\node_modules\@opentelemetry\api\build\src\internal\global-utils.js -> C:\Users\JBlanco\Documents\MFE - Product\node_modulules\@azure\core-http\node_modules\@opentelemetry\api\build\src\index.js
Any other information needed please let me know.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 20 (11 by maintainers)
I reopened the circular dependency issue in @opentelemetry/api as version 1.0.1 still contained circular dependencies. Since there’s nothing we can do on our side I think we can close this issue and track progress under https://github.com/open-telemetry/opentelemetry-js-api/issues/87
@jonathanblancor thanks for following up! Let’s see where we’re at:
Because @opentelemetry/api was in preview, @azure/identity is pinned against an exact version of @opentelemetry/api (indirectly, through core-tracing) so it will not get this fix directly.
All that to say - the issue was identified and fixed on @opentelemetry/api but it will take time for it to flow through our normal development and release process.
I reviewed @sadasant 's suggestion and I think suppressing the warning is a perfectly valid workaround to reduce bundling output noise as it has no impact at runtime. You can see how we did something similar in one of our rollup config files
I am keeping the issue open so we can revisit when @azure/identity 2.0.0 is released but I don’t expect that we will patch this as the currently GA’d Identity version is pinned against a preview version of @opentelemetry/api and there are incompatibilities between those versions and 1.0.1
Hope this information helps!