Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict with peer deps: zone.js@0.11.4 #1964

Closed
lugogregory opened this issue Feb 27, 2024 · 3 comments
Closed

Conflict with peer deps: zone.js@0.11.4 #1964

lugogregory opened this issue Feb 27, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@lugogregory
Copy link

What version of OpenTelemetry are you using?

"@opentelemetry/auto-instrumentations-web": "^0.36.0",
"@opentelemetry/context-zone": "^1.21.0",
"@opentelemetry/exporter-trace-otlp-http": "^0.48.0",
"@opentelemetry/instrumentation": "^0.48.0",
"@opentelemetry/sdk-trace-web": "^1.21.0",

What version of Node are you using?

v-18.6.0

What did you do?

I am trying to install: @opentelemetry/auto-instrumentations-web package to my project, with npm install.

What did you expect to see?

I expect I don´t receive any errors

What did you see instead?

I received a conflict with peer deps: zone.js@0.11.4

Additional context

When you try to install the metapackage: auto-instrumentation-web in an application that has a version of the zone.js library different from the one specified in the project's peer-deps, it generates a dependency conflict, even though the one you have in your project is higher than that of the metapackage.

You should consider changing the package.json (line 35) that currently has: "zone.js": "0.11.4" to "zone.js": "^0.11.4", so that it can use that version or one higher and does not generate conflicts when executing npm install

@lugogregory lugogregory added the bug Something isn't working label Feb 27, 2024
@JamieDanielson
Copy link
Member

I believe this is a duplicate of #1820 . This is on the radar and it looks like #1934 is prepped to update this, but we have to fix up a few things before we're able to get this in.

@lugogregory
Copy link
Author

Hi @JamieDanielson, thank you for your prompt and effective response. We hope for that change. Regards

@dyladan
Copy link
Member

dyladan commented Feb 28, 2024

Duplicate

@dyladan dyladan closed this as completed Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants