git404hub

what is turbopack-seal-bug fr?

gaearon/turbopack-seal-bug — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2026-06-16

★ 4JavaScriptAudience · developerComplexity · 2/5MaintainedSetup · easy

tl;dr

A bug report reproducing a Turbopack crash in Next.js 16 caused by wildcard re-exports mixing client and server code.

vibe map

mindmap
  root((turbopack-seal-bug))
    What it does
      Reproduces a Turbopack crash
      Bug report for Next.js 16
    Tech stack
      JavaScript
      Next.js
      Turbopack
    Use cases
      Diagnose build failures
      Understand the crash cause
      Find the workaround
    Audience
      Next.js developers
      Framework maintainers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Reproduce a Turbopack build crash caused by wildcard re-exports.

VIBE 2

Diagnose why a Next.js 16 build fails with a proxy-related error.

VIBE 3

Apply the workaround of using named re-exports instead of export * from.

what's the stack?

JavaScriptNext.jsTurbopack

how it stacks up fr

gaearon/turbopack-seal-bugarata-ae/purupurupngtubercarrycooldude/nova-ide
Stars444
LanguageJavaScriptJavaScriptJavaScript
Last pushed2026-06-16——
MaintenanceMaintained——
Setup difficultyeasymoderate—
Complexity2/53/5—
Audiencedevelopergeneralvibe coder

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

Reproduction only triggers when building with Turbopack under Next.js 16.

The README does not specify license terms for this repository.

prompts (copy fr)

prompt 1
Explain why Turbopack crashes when a module has both sealed and dynamic exports.
prompt 2
Help me find every export * from statement in my Next.js project that mixes client and server code.
prompt 3
Show me how to rewrite a wildcard re-export as explicit named exports to avoid this Turbopack bug.
prompt 4
Walk me through why this crash only happens with Turbopack and not Webpack.

Frequently asked questions

what is turbopack-seal-bug fr?

A bug report reproducing a Turbopack crash in Next.js 16 caused by wildcard re-exports mixing client and server code.

What language is turbopack-seal-bug written in?

Mainly JavaScript. The stack also includes JavaScript, Next.js, Turbopack.

Is turbopack-seal-bug actively maintained?

Maintained — commit in last 6 months (last push 2026-06-16).

What license does turbopack-seal-bug use?

The README does not specify license terms for this repository.

How hard is turbopack-seal-bug to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is turbopack-seal-bug for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.

similar repos, if this ain't it