-
Notifications
You must be signed in to change notification settings - Fork 847
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
deps: clean up dependencies #5484
deps: clean up dependencies #5484
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5484 +/- ##
=======================================
Coverage 94.97% 94.97%
=======================================
Files 309 309
Lines 8017 8017
Branches 1706 1706
=======================================
Hits 7614 7614
Misses 403 403 |
@@ -48,6 +48,7 @@ | |||
"@opentelemetry/api": "^1.3.0" | |||
}, | |||
"devDependencies": { | |||
"@opentelemetry/api": "1.9.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I would have figured that the peerDep would suffice here. From npm help json
section on peerDependencies
:
In npm versions 3 through 6, peerDependencies were not automatically
installed, and would raise a warning if an invalid version of the peer
dependency was found in the tree. As of npm v7, peerDependencies are
installed by default.
npm@7 was the default npm version as of Node.js v15.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I figured that too, and in normal operation this is not an issue. There was, however, some problem when I tried to simulate a release locally. It ended up having a package conflict without that dependency for some reason.
492ed35
Which problem is this PR solving?
@opentelemetry/api
was missing in@opentelemetry/sampler-jaeger-remote
@opentelemetry/[email protected]
was still thereType of change
How Has This Been Tested?