Packages

@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

Other targets from 0.8.1Newest 0.x0.8.4

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

  1. 1.0.4

    11 Nov 20263 fixes
    • Fixed

      Resolve runtime imports under paths with special chars

    • Fixed

      Allow @nuxt/cli v4 in peer dependencies

    • Fixed

      Rewrite #app to nuxt/app in build output

  2. 1.0.3

    23 Jul 20261 fix
    • Fixed

      Update command defaults and descriptions

  3. 1.0.2

    25 Jul 20251 fix
    • Fixed

      Use absolute path for jiti stub

  4. 1.0.1nothing new or fixed in the note

  5. 1.0.0

    Migration needed4 Apr 20252 new · 9 fixes
    • 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 __filename and __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.

  6. 0.8.4

    10 Sep 20241 fix
    • Fixed

      Remove nuxt/schema augment

  7. 0.8.3

    13 Aug 20241 fix
    • Fixed

      build: Handle missing named type exports

  8. 0.8.2

    13 Aug 20241 new · 1 fix
    • New

      Removed unnecessary hasTypeExport check

    • Fixed

      prepare: Override compatibilityDate

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.