Uh oh!
There was an error while loading. Please reload this page.
ref(nuxt): Build the Nuxt module in-house instead of @nuxt/module-builder - #22190
Merged
Conversation
logaretmforce-pushed
the
awad/nuxt-inhouse-build
branch
from
July 10, 2026 18:49
00fe4d9 to
102eb9cComparelogaretmforce-pushed
the
awad/nuxt-inhouse-build
branch
from
July 10, 2026 18:56
102eb9c to
10e5434Comparelogaretmforce-pushed
the
awad/nuxt-inhouse-build
branch
from
July 10, 2026 19:00
10e5434 to
b48cbc7CompareContributor
size-limit report 📦
|
logaretmforce-pushed
the
awad/nuxt-inhouse-build
branch
from
July 11, 2026 00:56
b48cbc7 to
18271b3Comparelogaretm
marked this pull request as ready for review
July 11, 2026 02:32
logaretm
requested review from
chargome, mydea and nicohrubec
and removed request for
a teamJuly 11, 2026 02:32
s1gr1d
approved these changes
Jul 13, 2026
Comment on lines
+6
to
+7
| // - `module.cjs`: a CJS shim. It can't statically require the ESM-only `@nuxt/kit`, | ||
| // so it lazily imports the ESM entry instead. |
Member
There was a problem hiding this comment.
We can remove the .cjs shim as they also made the module builder ESM-only in v1: https://github.com/nuxt/module-builder/releases/tag/v1.0.0
Apparently, this was only needed for Nuxt 2
MemberAuthor
There was a problem hiding this comment.
That's nice, I cleaned that up. thanks!
logaretmforce-pushed
the
awad/nuxt-inhouse-build
branch
from
July 13, 2026 14:09
18271b3 to
24b41c9Compare…lder Replace @nuxt/module-builder with a plain rollup + tsc setup for the build/module output: rollup bundles the module entry and emits the runtime files one-to-one (preserveModules), tsc emits the declarations, and a small script writes module.cjs, module.json and types.d.ts. This drops a build tool that consumes the TypeScript compiler API, so the package no longer pins us to a specific compiler.
logaretmforce-pushed
the
awad/nuxt-inhouse-build
branch
from
July 13, 2026 14:31
24b41c9 to
3131d3eCompare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces
@nuxt/module-builderwith a plain rollup + tsc setup for thebuild/moduleoutput. Rollup bundles the module entry and emits the runtime files one-to-one (preserveModules), tsc emits the declarations, and a small script writesmodule.cjs,module.jsonandtypes.d.ts.The point is to drop a build tool that consumes the TypeScript compiler API, so the package no longer pins us to a specific TS compiler, also streamlines nuxt SDK build step for future changes like rolldown.
We still have E2E tests ensuring the module output is consumable by Nuxt apps, so that's not something I would worry about drifting in the future.
Stacked on #22186.