Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#24,764 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
javascript, nextjs
Ambito
build-system, observability, performance

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
8.7k
Fork
1.9k
Merge medio
1g 17h
PR unite (30g)
543

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/sentry-javascript

Tutte le issue di getsentry/sentry-javascript

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.