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

Integrate with the Remix 3 asset server for debug IDs

Abierto
#24,667 1 comentario 0 reacciones 1 asignado Ver en GitHub

@chargome ya está trabajando en esto.

Desde el 23/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Remix

Hook into the Remix 3 asset server so browser modules carry debug IDs, with no config from the app.

  • Patch createAssetServer in @remix-run/assets and install our script loaders.
  • Inject a debug ID snippet into every served browser module.
  • Default sourceMaps to external. Remix's own template leaves source maps off in production, which would make every client stack trace unreadable.

Must follow the existing debug ID standard, so events symbolicate the same way they do for every other SDK:

  • UUID shaped ID
  • globalThis._sentryDebugIds keyed by stack, which is what getFilenameToDebugIdMap in @sentry/core reads at runtime
  • //# debugId= comment on the file and a debugId field in the source map, which is what sentry-cli reads at upload time

The ID must be a hash of the compiled source, not a UUID generated per process. The upload step runs in a separate process from the server, so a per process ID would never match what the browser reports.

scripts.loaders uses Node's synchronous load hook signature. It runs after the TypeScript transform and before minification, so the snippet is minified along with the module.

Done when e2e confirms every served module carries a debug ID, the ID is stable across requests, source maps are served without the app asking for them, and a captured client error carries debug_meta.images with a matching debug_id and code_file.

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

Guía de contribución

Abrir la guía de contribución

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.