Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#24,764 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
活発
技術スタック
javascript, nextjs
領域
build-system, observability, performance

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
TypeScript
スター
8.7k
フォーク
1.9k
平均マージ
1日 15時間
マージ済み PR（30日）
523

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

getsentry/sentry-javascript のほかの issue

getsentry/sentry-javascript の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。