Skip to content

turbopack-230526.2

  • turbopack-230526.2
  • a066e12
  • Partially verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
  • Choose a tag to compare

  • turbopack-230526.2
  • a066e12
  • Choose a tag to compare

  • Partially verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
@alexkirsz alexkirsz tagged this 26 May 10:12
### Description

This implements a Node.js production runtime for Turbopack, to first be
used for `next build --turbo`, but that can easily be extended to
support more production use cases (e.g. ncc).

The runtime works differently from the dev runtime we're currently using
for `next dev`: instead of having each chunk register itself against a
global registry when evaluated, chunks export their module factories as
a CommonJS default export. The runtime itself lives in a separate chunk,
and then an "exported chunk" is generated that instantiates runtime
entries and exports a given entry module.

Corresponding Next.js PR:
~~https://github.com/vercel/next.js/pull/49942~~
https://github.com/vercel/next.js/pull/50375

---------

Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
Assets 2
Loading