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

chore: sync package-lock.json #4947

Merged

Conversation

pichlermarc
Copy link
Member

@pichlermarc pichlermarc requested a review from a team August 22, 2024 08:56
@pichlermarc pichlermarc added this pull request to the merge queue Aug 22, 2024
Merged via the queue into open-telemetry:main with commit 5578a11 Aug 22, 2024
19 checks passed
@pichlermarc pichlermarc deleted the chore/sync-pkg-lock branch August 22, 2024 13:53
"packages/semantic-conventions": {
"name": "@opentelemetry/semantic-conventions",
"version": "1.25.1",
"extraneous": true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pichlermarc I've seen that in the past too. Note the "extraneous": true that (some version of) npm added. I'm not aware of npm or package-lock design docs that clarify these fields. A discourteous guess is that adding "extraneous" was a band-aid added in npm's package-lock handling at some point.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://github.com/npm/cli/blob/latest/workspaces/arborist/README.md is perhaps the best such doc. I haven't spent the time to learn it.

Zirak pushed a commit to Zirak/opentelemetry-js that referenced this pull request Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants