fix: add opentelemetry/core as a dependency to package.json #128
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solves #127
This will fix support for package managers like
pnpm
that require you to be very explicit about your dependenciesWhich problem is this PR solving?
package.json
is missing@opentelemetry/core
inpeerDependencies
#127Short description of the changes
Abides by requirements outlined here https://pnpm.io/how-peers-are-resolved
Given this package doesn't produce a bundle and is distributed using transpiled source code you still need the dependency manager to have the user resolve what is imported. The source code of this project directly imports this package https://github.com/search?q=repo%3Ahoneycombio%2Fhoneycomb-opentelemetry-web%20%22%40opentelemetry%2Fcore%22&type=code, thus this project relies on its presence.
How to verify that this has the expected result
Import this project and try to run it through webpack using
pnpm
as the package manager for the project. It will fail because the package I'm adding in this diff is never resolved in node_modules