Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Add source map upload for Remix 3

Ouverte
  • Quelque chose ne va pas ?
#24,678 1 commentaire 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@chargome y travaille déjà.

Depuis le 24/9/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

Remix

Remix 3 has no build step and produces no output directory, so there is nothing on disk for a source map upload to read. Rebuild that artifact set by driving the app's own asset server.

  • Add a command that imports the app's asset server module, forces the browser module graph, and writes each compiled module and its source map to a directory.
  • Stamp each file with //# debugId= and each map with a debugId field, so sentry-cli can pair them.
  • Upload the directory.

This has to be its own bin, separate from the existing sentry-upload-sourcemaps. That one is the Remix 2 command, takes --buildPath and --urlPrefix, and assumes a build directory that Remix 3 never produces. It cannot be overloaded without breaking Remix 2 users. Name the new one consistently with the v3 subpaths, so it is obvious which Remix each belongs to.

Uploading goes through the Sentry CLI, via the sentry package that @sentry/remix already depends on for the Remix 2 command. It needs SENTRY_ORG, SENTRY_PROJECT and SENTRY_AUTH_TOKEN. Note the CLI requires authentication even for sourcemap inject, so no part of this can run unauthenticated in tests. That is why verifying against a real org is tracked separately.

getPreloads() is what forces compilation. The asset server compiles lazily, so without it only the few modules something happened to request get emitted, and the upload is quietly almost empty.

The command must run under our --import entry. Importing the app's asset server in a plain Node process builds an unpatched asset server, and the output carries no debug IDs at all. Warn loudly when no debug IDs are found, because that failure is otherwise silent.

Done when the emitted directory has one map per module, every pair shares a debug ID, and the emitted ID matches what the running server serves.

Langage dominant
TypeScript
Étoiles
8.7k
Forks
1.9k
Merge moyen
1 j 17 h
PR mergées (30 j)
543

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de getsentry/sentry-javascript

Toutes les issues de getsentry/sentry-javascript

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.