Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

node-integration-tests: port HTTP and outgoing request suites to span streaming

Open
#24,135 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
node.js, typescript
Domain
api, backend, testing

Research direction

Start with the parent issue's porting recipe, then inspect the listed tracing, proxy, and ipv6 suites and their streamed twins. Follow the recipe across the named directories, fold back the two specified twins, and rename the three streamed-only suites when there are no collisions. Done means the listed HTTP and outgoing-request suites are ported consistently without duplicate suite names.

Written by the indexing model from the issue text.

Description

javascript Task

Follow the porting recipe in the parent issue.

Highest churn group, because http.server and http.client span names became low cardinality. Do this one first, since the other groups inherit its patterns.

Suites

  • tracing/requests/* (15 dirs)
  • tracing/http-client-spans/* (8 dirs)
  • tracing/httpIntegration
  • tracing/tracePropagationTargets and tracing/tracePropagationTargets/baggage-org-id
  • proxy
  • ipv6

Twins to fold back

  • tracing/httpIntegration-streamed into tracing/httpIntegration
  • tracing/http-client-spans/fetch-basic-streamed into tracing/http-client-spans/fetch-basic

tracing/http-client-span-streamed, tracing/httpServerSpans-streamed-unrouted and tracing/requestData-streamed have no static original. Rename them to drop the -streamed suffix once nothing collides.

Dominant language
TypeScript
Stars
8.7k
Forks
1.9k
Avg merge
1d 18h
Merged PRs (30d)
543

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-javascript

All issues in getsentry/sentry-javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.