chore(deps-dev): bump @nuxt/module-builder from 0.8.4 to 1.0.1

[dependabot]

Bumps @nuxt/module-builder from 0.8.4 to 1.0.1.

Release notes

Sourced from @​nuxt/module-builder's releases.

v1.0.1

compare changes

📖 Documentation

• Add full v1 release notes (#581, #582)
• Update to latest recommendations (6b30cde)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Connor Pearson (@​cjpearson)

v1.0.0

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 Changes

• Upgrade to unbuild v3 (#447) This major upgrade brings significant changes to the build proces but should be significantly better.

• Removal of Node10 module resolution and CommonJS output (#448) 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.

• 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.

🚧 Migration Guide

Replacing __filename and __dirname

We no longer polyfill these CommonJS variables. Instead, use the createResolver utility from @nuxt/kit:

import { createResolver } from '@nuxt/kit'
// Instead of __dirname and __filename
const resolver= createResolver(import.meta.url)
const runtimeDir = resolver.resolve('./runtime')

Module Resolution Changes

We no longer officially support Node10 module resolution, meaning you should remove the types/type field from your package.json. If you need to maintain compatibility with older Node.js versions or systems expecting CommonJS, you can use the typesVersions field in your package.json.

This field allows typing subpath exports (like my-module/utils) even with older moduleResolution settings. Regardless, we recommend all Nuxt users to use Bundler module resolution.

{
  "typesVersions": {
    "*": {
</tr></table> 

... (truncated)

Changelog

Sourced from @​nuxt/module-builder's changelog.

v1.0.1

compare changes

📖 Documentation

• Add full v1 release notes (#581, #582)
• Update to latest recommendations (6b30cde)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Connor Pearson (@​cjpearson)

v1.0.0

compare changes

🚀 Enhancements

• ⚠️ Upgrade to unbuild v3 (#447)
• ⚠️ Remove support for node10 resolution + cjs (#448)
• build: Ignore test + story files in runtime/ directory (#480)
• Add support for type exports in module re-exports (#563)

🩹 Fixes

• Mark nuxi as optional peerDep (29a42ae)
• Drop @​nuxt/kit peer dependency & remove optionality for nuxi (5936063)
• build: Handle windows path names (#399)
• build: Apply resolved tsconfig to dts (#462)
• Handle node10 resolution + add attw test (7309198)
• Update warnings (6291cbe)
• Support more than one line of type exports (0c0020f)
• Split re-exports across multiple lines (7154a89)
• Support star exports (8966047)

📖 Documentation

• Update example build script (#359)
• Update link to downloads count badge (9804e9e)(b9b27c3)
• Describe configuring unbuild (#440)

🏡 Chore

• Use tinyexec in test suite (7ff8ef1)
• Fix links (2e57eb2)
• Pin typescript until issue with vue-tsc is resolved (994135d)
• Bump vue-tsc (e8cb0ef)
• Bump nuxi version (5b1f00e)

... (truncated)

Commits

• 7a43cbf chore(release): v1.0.1
• c0cac22 chore(deps): update dependency vue-sfc-transformer to ^0.1.8 (#590)
• 3771544 chore(deps): update pnpm to v10.8.0 (#589)
• 2d3daca chore(deps): lock file maintenance (#586)
• 36eebcd chore(deps): update dependency vue-sfc-transformer to ^0.1.5 (#585)
• 3dc71f9 chore(deps): update devdependency knip to ^5.47.0 (#584)
• 6b30cde docs: update to latest recommendations
• 48e98e5 docs: add full v1 release notes (#581) (#582)
• aac840d chore(deps): update resolutions typescript to v5.8.3 (#579)
• b0655d3 chore(release): v1.0.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)