What problem does it solve?
Maintaining npm dependencies on pre-v1 OpenTelemetry instrumentation packages creates upgrade risk and dependency bloat in the Sentry JavaScript SDK. This Skill automates the process of copying upstream OTel instrumentation TypeScript source directly into the SDK as vendored code, removing the npm dependency while preserving identical behavior.
Core Features & Use Cases
- Upstream Research and Diffing: Fetches source files from the opentelemetry-js-contrib GitHub repo, compares pinned versus latest versions, and reviews changelogs before vendoring.
- License-Compliant Vendoring: Copies TypeScript source with full Apache 2.0 headers, Sentry NOTICE blocks, and standard replacements like SDK_VERSION from @sentry/core.
- External Type Inlining: Inlines simplified types from external packages into dedicated type files so builds do not rely on workspace hoisting.
- Build and Test Verification: Runs yarn build, integration tests, and unit tests, then creates a draft PR against the develop branch.
- Use Case: When you need to vendor @opentelemetry/instrumentation-graphql into @sentry/node, this Skill walks through research, planning, copying, type inlining, testing, and PR creation with user approval gates.
Quick Start
Vendor the @opentelemetry/instrumentation-kafkajs package into the Sentry Node SDK and create a draft PR.