Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Next.js v11 build-time instrumentation: Turbopack build timeout and opt-out trace coverage

Offen
  • Stimmt etwas nicht?
#24,764 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
javascript, nextjs
Bereich
build-system, observability, performance

Rechercherichtung

Start with maybeAddOrchestrionRule in constructTurbopackConfig and compare the default node rule with the reported node_modules path-filtering experiment. Reproduce clean Turbopack production builds with buildTimeInstrumentation enabled and disabled, then inspect generated output for the named AI SDK, OpenAI, Anthropic, and database integrations. Done means a documented minimal reproduction or profiling result plus an explicit account of trace coverage and supported configuration.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Bug Next.js Waiting for: Product Owner
Environment
  • @sentry/nextjs 11.0.0
  • Next.js 16.3.6, Turbopack production build
  • pnpm workspace monorepo
  • Vercel build machine: 4 cores, 8 GB
Observed regression

Our first production Git deployment upgrading from Sentry 10 to 11 stopped at Creating an optimized production build and was terminated with BUILD_EXCEEDED_MAXIMUM_TIME (45 minutes). The preceding build, also without cache, compiled in 2.2 minutes. There is no explicit Vercel OOM error.

Isolation and mitigation

A clean local build with 4-CPU affinity, an 8-GB memory cgroup, no swap, and production environment completed with only buildTimeInstrumentation: false changed (98-second compilation).

We inspected maybeAddOrchestrionRule in constructTurbopackConfig: the *.{js,mjs,cjs} rule has condition node. An experimental local patch added a node_modules path condition derived from getSentryInstrumentations() module names. A subsequent clean source build on Vercel compiled in 107 seconds and completed in 4m15s; AI SDK/OpenAI/Anthropic registration calls were present in generated output. This suggests the broad loader rule may contribute, but we have not profiled the precise bottleneck or produced a public minimal reproduction.

We are removing that custom patch and using the supported buildTimeInstrumentation: false option while investigating.

Questions
  1. Is excessive Turbopack loader work with the default Orchestrion rule a known v11 issue? Is package-level filtering supported or planned?
  2. Which automatic server traces are lost with buildTimeInstrumentation: false on Vercel, particularly bundled AI SDK 7, OpenAI and Anthropic SDKs, and database clients? Which still work through runtime channels or Next.js instrumentation?
  3. Is there a supported selective option to preserve these integrations without passing every server JavaScript module through the loader?
  4. What profiling output or minimal reproduction would be most useful?

Error reporting, source map upload and explicit application spans remain configured. We are not claiming this mitigation preserves all automatic trace coverage.

Vorherrschende Sprache
TypeScript
Sterne
8.7k
Forks
1.9k
Ø Merge
1 T. 15 Std.
Gemergte PRs (30 T.)
523

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus getsentry/sentry-javascript

Alle Issues in getsentry/sentry-javascript

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.