sigcue
← Reported problems
Reported problemNot a verified signal

Inline <Script strategy="beforeInteractive"> bodies ship twice: executable __next_s push in <head> plus an unused copy in the RSC flight payload

Inline <Script strategy="beforeInteractive"> bodies ship twice: executable __next_s push in <head> plus an unused copy in the RSC flight payload

SourceGitHub
Communityvercel/next.js
DateAug 5, 2026
Independent reports1

Important limitations

  • This may be one public report, not widespread demand.
  • Current independent report count: 1.
  • This is currently a single independent report. It has not passed clustering or human review as a verified signal.
  • No market size, willingness to pay, competition, or trend claims are inferred here.

What was reported

Who is affected
Frontend application developer
Job to be done
Preserve type safety while building an application
Workflow
typescript: 7.0.2
Desired outcome
** the body ships once. As far as we can determine, the flight copy of an inline `beforeInteractive` body is never read in production: - `self.__next_s` has a single reader — `loadScriptsInSequence` in [`app-bootstrap`](https://github.com/vercel/next.js/blob/canary/packages/next/src/client/app-bootstrap.ts) — which executes the scripts before hydration begins. - During hydration React matches the already-present `<script>` element; it does not re-execute or diff the inline body against the flight copy (inline-content mismatch warnings are dev-only). - Client-side
Severity
Not enough evidence yet.
Urgency
Not enough evidence yet.

Evidence indicators

Evidence records1
Independent reports1
Reproduction notesPresent
Metrics mentionedNot observed
Logs mentionedPresent
Corroborationuncorroborated

What would upgrade this

  • Additional independent reports from distinct communities or authors.
  • Human clustering into a review signal, then explicit publication approval.
  • Counter-evidence review and durable original-source verification.

Original source

Open the original public report