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

browser-integration-tests: drop static pins from non-tracing suites

Open
#24,145 1 comment 0 reactions 1 assignee View on GitHub

@msonnb is already working on this.

Since Sep 7, 2026.

Assessment

This issue has not been assessed yet.

Description

javascript Task

Follow the porting recipe in the parent issue.

Largest group by file count and the smallest by effort. Around 226 pinned init.js files never assert on a transaction envelope, so the pin just needs to go.

Suites (pin removal only)

  • replay/* (78 files, the single biggest block)
  • feedback/*, sessions/*, errors/*, stacktraces/*, transport/*, wasm/*, old-sdk-interop/*, manual-client/*, ipv6
  • public-api/* except the span surface dirs owned by the trace semantics sub-issue
  • integrations/* except httpclient, which the trace semantics sub-issue owns

Watch-outs

  • replay/dsc and public-api/dataCollection do assert on the trace context, so they need a rewrite rather than a pin removal.
  • profiling/traceLifecycleMode_multiple-chunks and traceLifecycleMode_overlapping-spans intentionally test the static lifecycle. Leave their pins in place.
  • integrations/cultureContext-streamed and integrations/httpContext-streamed are twins. Fold them back into their static originals.
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.