package.json should separate dependencies to peerDependencies

[Aghassi]

honeycomb-opentelemetry-web/package.json

Lines 39 to 53 in e46248c

	"dependencies": {
	"@opentelemetry/api": "~1.8.0",
	"@opentelemetry/exporter-trace-otlp-http": "~0.50.0",
	"@opentelemetry/instrumentation": "~0.50.0",
	"@opentelemetry/opentelemetry-browser-detector": "~0.50.0",
	"@opentelemetry/resources": "~1.23.0",
	"@opentelemetry/sdk-trace-base": "~1.23.0",
	"@opentelemetry/sdk-trace-web": "~1.23.0",
	"@opentelemetry/semantic-conventions": "~1.23.0",
	"@typescript-eslint/eslint-plugin": "^7.0.2",
	"@typescript-eslint/parser": "^7.0.2",
	"axios": "^1.6.7",
	"eslint-config-prettier": "^9.1.0",
	"prettier": "^3.2.4",
	"web-vitals": "^3.5.2"

There a number of @opentelemetry packages in the package.json of this package. However, they are called in the code that is unbundled. If they are expected to be provided by the consumer, then these should be specified as peerDependencies. https://pnpm.io/how-peers-are-resolved

This prevents version duplication as well as forces the end user to specify what version they are on.

[martin308]

We've taken a look at this and all of the open telemetry libraries are core dependencies that are part of the bundle. The only one we could look at removing (not moving to peer) is @opentelemetry/auto-instrumentations-web but it is complicated as we do include that in the CDN distribution that we build.

We will keep an eye out in the future on our dependencies and if we can remove/move any of them. Thanks for raising this