Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Run the orchestrion transform on browser modules

Abierto
  • ¿Algo no está bien?
#24,677 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@chargome ya está trabajando en esto.

Desde el 24/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Remix

Run the orchestrion code transform on browser modules, through the asset server's loader chain, so client side instrumentation works without a bundler.

  • Add a loader that applies the transform to modules under node_modules, resolving the package name and version from the file path.
  • Point orchestrion's dcModule at our browser diagnostics_channel shim.
  • Patch run in @remix-run/ui so component render errors are captured with no application code.

This is the only compile time hook in the Remix 3 client pipeline. It also matters for remix/spa, where the same fetch-router runs in the browser and the Node module hook can never reach it.

Three things have to line up, and each one fails differently:

  • The shim must implement the low level channel API the injected code calls: ch.start.runStores, ch.error.publish, ch.end.publish. The traceSync helpers are not what it uses.
  • ModuleType must be lower case esm. Anything else silently emits a CommonJS require, which the asset server cannot serve.
  • The shim is referenced by public URL and must be in scripts.external, percent encoded exactly as the asset server encodes its own rewrites. A bare specifier does not resolve under pnpm. A mismatch loads two copies of the shim, giving two subscriber registries and no instrumentation, with no error anywhere.

Done when e2e confirms the transform is applied to a served browser module, the injected channel fires in the browser, and a component render error reaches Sentry with mechanism auto.ui.remix_v3.

Lenguaje dominante
TypeScript
Estrellas
8.7k
Forks
1.9k
Merge medio
1 d 17 h
PR fusionados (30 d)
543

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de getsentry/sentry-javascript

Todos los issues de getsentry/sentry-javascript

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.