- Notifications
You must be signed in to change notification settings - Fork2.6k
fix(nx-dev): remove OTel-based tracing for now to remove local dev erros#30096
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
vercelbot commentedFeb 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The latest updates on your projects. Learn more aboutVercel for Git ↗︎
|
nx-cloudbot commentedFeb 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
View yourCI Pipeline Execution ↗ for commit11b5df3.
☁️Nx Cloud last updated this comment at |
51a0bae
intomasterUh oh!
There was an error while loading.Please reload this page.
…ros (#30096)Locally, when running `nx serve-docs nx-dev`, you'll see errors comingfrom `/blog` URLs due to instrumentation problems. This is caused by the`@grafana/faro-web-tracing` packages as soon as it is imported in an approuter environment.We don't need it for now, so we can just remove it. It means that wewill be missing tracing on HTTP requests like XHRs, but we still getperformance metrics and error reporting.## Current BehaviorSee errors in logs during development## Expected BehaviorNo errors in logs## Related Issue(s)<!-- Please link the issue being fixed so it gets closed when this ismerged. -->Fixes #
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Locally, when running
nx serve-docs nx-dev
, you'll see errors coming from/blog
URLs due to instrumentation problems. This is caused by the@grafana/faro-web-tracing
packages as soon as it is imported in an app router environment.We don't need it for now, so we can just remove it. It means that we will be missing tracing on HTTP requests like XHRs, but we still get performance metrics and error reporting.
Current Behavior
See errors in logs during development
Expected Behavior
No errors in logs
Related Issue(s)
Fixes #