@nuxt/module-builder
1.0.4 · 11 Nov 2026MIT146.9k / weekRepositoryHomepagenpmAtom feed
Upgrading @nuxt/module-builder From 0.8.1 to 1.0.4
8 releases in betweenevery note read
- 8
- changes to make
- 0
- advisories fixed
- 3
- new
- 17
- fixes
Before you upgrade
Tick each one off as you go- Breaking1.0.0
- Breaking1.0.0
- Breaking1.0.0
- Breaking1.0.0
- Breaking1.0.0
- Breaking1.0.0
- Breaking1.0.0
- Breaking1.0.0
Release by release
- Fixed
Update command defaults and descriptions
- Fixed
- Fixed
Use absolute path for jiti stub
- Fixed
1.0.1nothing new or fixed in the note
- Breaking
With the release of unbuild v3, the EOL status of Nuxt 2, and looking forward to Nuxt 4, we're taking the opportunity to release v1 of
@nuxt/module-builder, with a range of breaking changes. - Breaking
Upgrade to unbuild v3 This major upgrade brings significant changes to the build proces but should be significantly better.
- Breaking
Removal of Node10 module resolution and CommonJS output As Nuxt 2 has reached EOL, we no longer generate CJS by default, and we have also removed the 'CJS bridge' feature that polyfilled
__filenameand__dirname. - Breaking
Type errors. The module builder will now error if there are type errors when generating your
runtime/*files. (Previously warnings were logged but your build would have succeeded.) Errors you receive aren't caused by the upgrade, but you might need to correct any issues before your module will build again.
- Breaking
- Fixed
Remove
nuxt/schemaaugment
- Fixed
- Fixed
build: Handle missing named type exports
- Fixed
- New
Removed unnecessary hasTypeExport check
- Fixed
prepare: Override
compatibilityDate
- New
56 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.