Comments (8)
Hi, this is a very recent issue I see :)
I too am having the same issue, even though using @opentelemetry/[email protected]
. Also have @opentelemetry/api
installed and the problem still persists.
I removed all my node_modules
and ran pnpm install
again, no luck :(
from otel.
For yarn
, add the following in your package.json
"resolutions": {
"@opentelemetry/resources": "<=1.14.0",
"@opentelemetry/sdk-trace-node": "<=1.14.0",
"@opentelemetry/semantic-conventions": "<=1.14.0"
}
For npm
or pnpm
use "overrides" instead:
"overrides": {
"@opentelemetry/resources": "<=1.14.0",
"@opentelemetry/sdk-trace-node": "<=1.14.0",
"@opentelemetry/semantic-conventions": "<=1.14.0"
}
This will make sure that all the opentelemetry dependencies that @vercel/otel
uses are the versions previous to 0.15.0
from otel.
Thanks for presenting the code.
I tried it in yarn and it worked fine!
I appreciate your support.
from otel.
For
yarn
, add the following in your package.json"resolutions": { "@opentelemetry/resources": "<=1.14.0", "@opentelemetry/sdk-trace-node": "<=1.14.0", "@opentelemetry/semantic-conventions": "<=1.14.0" }For
npm
orpnpm
use "overrides" instead:"overrides": { "@opentelemetry/resources": "<=1.14.0", "@opentelemetry/sdk-trace-node": "<=1.14.0", "@opentelemetry/semantic-conventions": "<=1.14.0" }This will make sure that all the opentelemetry dependencies that
@vercel/otel
uses are the versions previous to0.15.0
Thanks, i can verify this works. Except the format for pnpm should be:
"pnpm": {
"overrides": {
"@opentelemetry/resources": "<=1.14.0",
"@opentelemetry/sdk-trace-node": "<=1.14.0",
"@opentelemetry/semantic-conventions": "<=1.14.0"
}
}
Confirmed working!
from otel.
You can also resolve this by using the transpilePackages
config:
transpilePackages: ['@vercel/otel'],
from otel.
@herzog0 Thanks for reporting this issue. It is originating from @opentelemetry/resources
package: open-telemetry/opentelemetry-js#3976
For now, we recommend downgrading @opentelemetry/resources
to 1.14.0
. Once the issue is fixed, you can remove the pinned version from your dependencies.
from otel.
@mdahiemstra Can you run pnpm list @opentelemetry/resources
and share the result please?
from otel.
I am in the same situation.
I think this is happening because @opentelemetry/sdk-trace-base v1.15.0
on which @opentelemetry/sdk-trace-node@^1.12.0
specified in @vercel/otel
depends which @opentelemetry/sdk-trace-base v1.15.0
depends on.
(I'm a newbie, so sorry if I'm saying something wrong)
Below I have pasted the contents of yarn.lock with excerpts where necessary.
"@vercel/otel@^0.3.0":
version "0.3.0"
resolved "https://registry.yarnpkg.com/@vercel/otel/-/otel-0.3.0.tgz#48fcac8fe7e0c4735a586be916930922cba0106c"
integrity sha512-KgLZjBXmMPKCh9uswY81I6oaVZdH2Eyn4snbx86n20t2LW8iEmjSxzxuviET+lfiIQwWWCiZkC6+SiPXOc7naA==
dependencies:
"@opentelemetry/api" "^1.4.1"
"@opentelemetry/exporter-trace-otlp-grpc" "^0.38.0"
"@opentelemetry/resources" "^1.12.0"
"@opentelemetry/sdk-node" "^0.38.0"
"@opentelemetry/sdk-trace-node" "^1.12.0"
"@opentelemetry/semantic-conventions" "^1.12.0"
"@opentelemetry/sdk-trace-node@^1.12.0":
version "1.15.0"
resolved "https://registry.yarnpkg.com/@opentelemetry/sdk-trace-node/-/sdk-trace-node-1.15.0.tgz#2d49eafb070a6a53e8df7e91dab30ec2370ba310"
integrity sha512-TKBx9oThZUVKkoGpXhFT/XUgpjq28TWwc6j3JlsL+cJX77DKBnVC+2H+kdVVJHRzyfqDx4LEJJVCwQO3K+cbXA==
dependencies:
"@opentelemetry/context-async-hooks" "1.15.0"
"@opentelemetry/core" "1.15.0"
"@opentelemetry/propagator-b3" "1.15.0"
"@opentelemetry/propagator-jaeger" "1.15.0"
"@opentelemetry/sdk-trace-base" "1.15.0"
semver "^7.5.1"
tslib "^2.3.1"
"@opentelemetry/[email protected]":
version "1.15.0"
resolved "https://registry.yarnpkg.com/@opentelemetry/sdk-trace-base/-/sdk-trace-base-1.15.0.tgz#92340ded8f9fec1aaa63afb40c6e7e01769c2852"
integrity sha512-udt1c9VHipbZwvCPIQR1VLg25Z4AMR/g0X8KmcInbFruGWQ/lptVPkz3yvWAsGSta5yHNQ3uoPwcyCygGnQ6Lg==
dependencies:
"@opentelemetry/core" "1.15.0"
"@opentelemetry/resources" "1.15.0"
"@opentelemetry/semantic-conventions" "1.15.0"
tslib "^2.3.1"
from otel.
Related Issues (11)
- OTel support in the edge runtime HOT 2
- jaeger.thrift no such file or directory HOT 1
- Incorrect Peer Dependencies when Installing HOT 1
- Pass in additional resource attributes HOT 4
- Inbound header to attr mapping
- traceExporter is ignored when `VERCEL_OTEL_ENDPOINTS` is available
- Not recording fetch HOT 1
- Error with next build: Legacy octal escape is not permitted in strict mode HOT 9
- Not able to install due to broken dependencies
- Package overrides fetch polyfill on edge worker with broken version
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from otel.