-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
feat(telemetry): add JS package #7820
feat(telemetry): add JS package #7820
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
7 Ignored Deployments
|
✅ This change can build |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
|
🟢 Turbopack Benchmark CI successful 🟢Thanks |
a90ae13
to
2f5cf3b
Compare
🟢 CI successful 🟢Thanks |
2f5cf3b
to
dd3ff0d
Compare
dd3ff0d
to
55f289c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I do have some slight concern about keeping the event keys in sync. There's probably something we could do with napi
, but no need to build infra before we need it.
55f289c
to
b138c2e
Compare
@chris-olszewski the intention isn't to mirror events here one to one, but for the events tracked in the JS packages to be unique and specific to the JS packages. These also use a different event type on the backend that always tracks the package name and version as context. I did think about napi for some of the shared code (like config) but the lift was low and didn't want to deal with the multi os / arch support here. |
Description
Adds a
turbo-telemetry
library that enables tracking telemetry events from javascript packages.Important
This shares all telemetry state with turbo core's telemetry. This means users only need to disable once across all packages.