@nuxt/docs-nightly 4.4.7-29652887.e4d5cc70 → 4.4.7-29673443.69f58084

package/3.guide/4.modules/3.recipes-basics.md

@@ -393,47 +393,19 @@ export default defineNuxtModule({
 
 ## Use Other Modules
 
-If your module depends on other modules, you can specify them using the `moduleDependencies` option. This provides a more robust way to handle module dependencies with version constraints and configuration merging:
+If your module depends on other modules, you can specify them using the `moduleDependencies` option:
 
 ```ts
-import { createResolver, defineNuxtModule } from '@nuxt/kit'
-
-const resolver = createResolver(import.meta.url)
+import { defineNuxtModule } from '@nuxt/kit'
 
-export default defineNuxtModule<ModuleOptions>({
+export default defineNuxtModule({
   meta: {
     name: 'my-module',
   },
   moduleDependencies: {
-    '@nuxtjs/tailwindcss': {
-      // You can specify a version constraint for the module
-      version: '>=6',
-      // Any configuration that should override `nuxt.options`
-      overrides: {
-        exposeConfig: true,
-      },
-      // Any configuration that should be set. It will override module defaults but
-      // will not override any configuration set in `nuxt.options`
-      defaults: {
-        config: {
-          darkMode: 'class',
-          content: {
-            files: [
-              resolver.resolve('./runtime/components/**/*.{vue,mjs,ts}'),
-              resolver.resolve('./runtime/*.{mjs,js,ts}'),
-            ],
-          },
-        },
-      },
-    },
-  },
-  setup (options, nuxt) {
-    // We can inject our CSS file which includes Tailwind's directives
-    nuxt.options.css.push(resolver.resolve('./runtime/assets/styles.css'))
+    '@nuxtjs/tailwindcss': {},
   },
 })
 ```
 
-::callout{type="info"}
-The `moduleDependencies` option replaces the deprecated `installModule` function and ensures proper setup order and configuration merging.
-::
+:read-more{to="/docs/4.x/guide/modules/module-dependencies"}

package/3.guide/4.modules/4.module-dependencies.md

@@ -0,0 +1,84 @@
+---
+title: 'Module Dependencies'
+description: 'Declare dependencies on other modules with version constraints and configuration merging.'
+---
+
+If your module depends on other modules, you can declare them using the `moduleDependencies` option. Nuxt then ensures those modules are installed in the correct order, validates any version constraints you provide, and merges configuration you supply for them.
+
+## Basic Usage
+
+```ts
+import { createResolver, defineNuxtModule } from '@nuxt/kit'
+
+const resolver = createResolver(import.meta.url)
+
+export default defineNuxtModule<ModuleOptions>({
+  meta: {
+    name: 'my-module',
+  },
+  moduleDependencies: {
+    '@nuxtjs/tailwindcss': {
+      // You can specify a version constraint for the module
+      version: '>=6',
+      // Any configuration that should override `nuxt.options`
+      overrides: {
+        exposeConfig: true,
+      },
+      // Any configuration that should be set. It will override module defaults but
+      // will not override any configuration set in `nuxt.options`
+      defaults: {
+        config: {
+          darkMode: 'class',
+          content: {
+            files: [
+              resolver.resolve('./runtime/components/**/*.{vue,mjs,ts}'),
+              resolver.resolve('./runtime/*.{mjs,js,ts}'),
+            ],
+          },
+        },
+      },
+    },
+  },
+  setup (options, nuxt) {
+    // We can inject our CSS file which includes Tailwind's directives
+    nuxt.options.css.push(resolver.resolve('./runtime/assets/styles.css'))
+  },
+})
+```
+
+::callout{type="info"}
+The `moduleDependencies` option replaces the deprecated `installModule` function.
+::
+
+The key of each entry identifies the module to depend on. You can use an npm package name, a path to a local module directory, or a Nuxt alias such as `~` or `@`.
+
+## Depending on Local Modules
+
+When the dependency lives inside  the [`modules/` directory](/docs/4.x/guide/directory-structure/modules), use a file path to declare the dependency:
+
+```ts
+import { defineNuxtModule } from '@nuxt/kit'
+
+export default defineNuxtModule({
+  moduleDependencies: {
+    // Path relative to the project root
+    './modules/my-local-module': {},
+    // Or using a Nuxt alias
+    '~/modules/another-local-module': {},
+  },
+  // ...
+})
+```
+
+::important
+**Relative paths are resolved from your project's `rootDir`**, not from the file declaring the dependency. A module at `modules/foo.ts` referencing `modules/bar.ts` must use `'./modules/bar'`, not `'./bar'`. Using a Nuxt alias such as `~/modules/bar` avoids this ambiguity.
+::
+
+## Options
+
+Each entry in `moduleDependencies` accepts the following fields:
+
+- `version`: A semver range. If the resolved module's version does not satisfy this range, Nuxt throws an error. Version checks only apply when the dependency can be resolved to a `package.json`, so they are a no-op for project-local modules.
+- `overrides`: Configuration applied on top of `nuxt.options`, taking precedence over user configuration.
+- `defaults`: Configuration applied below `nuxt.options`. User configuration takes precedence over these.
+- `optional`: If `true`, the module is not installed automatically when missing. `overrides` and `defaults` are still applied if the module is installed elsewhere.

package/3.guide/4.modules/index.md

@@ -21,6 +21,9 @@ With modules, you can encapsulate, properly test, and share custom solutions as
   ::card{icon="i-lucide-code" title="Add Plugins, Components & More" to="/docs/4.x/guide/modules/recipes-basics"}
   Learn how to inject plugins, components, composables and server routes from your module.
   ::
+  ::card{icon="i-lucide-link" title="Depend on Other Modules" to="/docs/4.x/guide/modules/module-dependencies"}
+  Declare dependencies on other modules with version constraints and configuration merging.
+  ::
   ::card{icon="i-lucide-layers" title="Use Hooks & Extend Types" to="/docs/4.x/guide/modules/recipes-advanced"}
   Master lifecycle hooks, virtual files and TypeScript declarations in your modules.
   ::

package/4.api/5.kit/12.resolving.md

@@ -8,11 +8,11 @@ links:
     size: xs
 ---
 
-Sometimes you need to resolve a paths: relative to the current module, with unknown name or extension. For example, you may want to add a plugin that is located in the same directory as the module. To handle this cases, nuxt provides a set of utilities to resolve paths. `resolvePath` and `resolveAlias` are used to resolve paths relative to the current module. `findPath` is used to find first existing file in given paths. `createResolver` is used to create resolver relative to base path.
+Sometimes you need to resolve a path relative to the current module without knowing the name or extension. For example, you may want to add a plugin that is located in the same directory as the module. To handle these cases, Nuxt provides a set of utilities to resolve paths. `resolvePath` and `resolveAlias` are used to resolve paths relative to the current module. `findPath` is used to find the first existing file in a given set of paths. `createResolver` is used to create a resolver relative to the base path.
 
 ## `resolvePath`
 
-Resolves full path to a file or directory respecting Nuxt alias and extensions options. If path could not be resolved, normalized input path will be returned.
+Resolves the full path to a file or directory, respecting Nuxt alias and extensions options. If a path could not be resolved, a normalized input path will be returned.
 
 ### Usage
 
@@ -115,7 +115,7 @@ function resolveAlias (path: string, alias?: Record<string, string>): string
 
 ## `findPath`
 
-Try to resolve first existing file in given paths.
+Try to resolve first existing file in a given set of paths.
 
 ### Usage
 

package/4.api/6.nuxt-config.md

@@ -313,7 +313,7 @@ This can be overridden with `definePageMeta` on an individual page.
 - **Type**: `boolean`
 - **Default:** `false`
 
-**See**: [Nuxt View Transition API docs](https://nuxt.com/docs/4.x/getting-started/transitions#view-transitions-api-experimental)
+**See**: [Nuxt View Transition API docs](/docs/4.x/getting-started/transitions#view-transitions-api-experimental)
 
 ## appConfig
 
@@ -506,7 +506,7 @@ Any components in the directories configured here can be used throughout your pa
 }
 ```
 
-**See**: [`app/components/` directory documentation](https://nuxt.com/docs/4.x/directory-structure/app/components)
+**See**: [`app/components/` directory documentation](/docs/4.x/directory-structure/app/components)
 
 ## css
 
@@ -837,7 +837,7 @@ Any file in `app/pages/`, `app/layouts/`, `app/middleware/`, and `public/` direc
 
 Configure how Nuxt auto-imports composables into your application.
 
-**See**: [Nuxt documentation](https://nuxt.com/docs/4.x/directory-structure/app/composables)
+**See**: [Nuxt documentation](/docs/4.x/directory-structure/app/composables)
 
 ### `dirs`
 
@@ -1159,7 +1159,7 @@ and these plugins do not need to be listed in `nuxt.config` unless you
 need to customize their order. All plugins are deduplicated by their src path.
 ::
 
-**See**: [`app/plugins/` directory documentation](https://nuxt.com/docs/4.x/directory-structure/app/plugins)
+**See**: [`app/plugins/` directory documentation](/docs/4.x/directory-structure/app/plugins)
 
 **Example**:
 ```ts
@@ -1320,7 +1320,7 @@ Each handler accepts the following options:
 
 - **Type**: `array`
 
-**See**: [`server/` directory documentation](https://nuxt.com/docs/4.x/directory-structure/server)
+**See**: [`server/` directory documentation](/docs/4.x/directory-structure/server)
 
 ::callout
 **Note**: Files from `server/api`, `server/middleware` and `server/routes` will be automatically registered by Nuxt.
@@ -1521,6 +1521,18 @@ Include parent workspace in the Nuxt project. Mostly useful for themes and modul
 - **Type**: `boolean`
 - **Default:** `false`
 
+### `nodeTsConfig`
+
+You can extend the generated `.nuxt/tsconfig.node.json` TypeScript configuration using this option.
+
+**See**: [tsconfig.json information](/docs/4.x/directory-structure/tsconfig)
+
+### `sharedTsConfig`
+
+You can extend the generated `.nuxt/tsconfig.shared.json` TypeScript configuration using this option.
+
+**See**: [tsconfig.json information](/docs/4.x/directory-structure/tsconfig)
+
 ### `shim`
 
 Generate a `*.vue` shim.
@@ -1542,7 +1554,9 @@ TypeScript comes with certain checks to give you more safety and analysis of you
 
 ### `tsConfig`
 
-You can extend the generated TypeScript configurations (`.nuxt/tsconfig.app.json`, `.nuxt/tsconfig.server.json`, etc.) using this option.
+You can extend the generated `.nuxt/tsconfig.app.json` TypeScript configuration using this option.
+
+**See**: [tsconfig.json information](/docs/4.x/directory-structure/tsconfig)
 
 ### `typeCheck`
 
@@ -1553,7 +1567,7 @@ If set to true, this will type check in development. You can restrict this to bu
 - **Type**: `boolean`
 - **Default:** `false`
 
-**See**: [Nuxt TypeScript docs](https://nuxt.com/docs/4.x/guide/concepts/typescript)
+**See**: [Nuxt TypeScript docs](/docs/4.x/guide/concepts/typescript)
 
 ## unhead
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "4.4.7-29652887.e4d5cc70",
+  "version": "4.4.7-29673443.69f58084",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",