Server modules

This page documents embedded server modules, its configuration contract and the recommended usage pattern for application developers.

Purpose

Embedded server modules helps keep the Nuxt module configuration, Feathers runtime, generated services, TypeScript client and CLI workflow aligned.

When to use this option

Use this page when you need to:

• configure embedded server modules;
• document the decision in a starter or application;
• validate the setup with a CLI command;
• avoid drift between configuration, generated files and runtime behavior.

Configuration example

// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['nuxt-feathers-zod'],

  feathers: {
    server: {
      modules: [
        'helmet',
        { src: 'rate-limit', options: { windowMs: 60_000, max: 120 } },
      ],
      loadOrder: ['modules:pre', 'plugins', 'services', 'modules:post'],
    },
  }
})

CLI example

bunx nuxt-feathers-zod add server-module rate-limit --preset rate-limit --force

Runtime example

const service = useService('messages')

const result = await service.find({
  query: {
    $limit: 10,
    $sort: { createdAt: -1 },
  },
})

Practical advice

• Keep runtime-affecting options explicit in nuxt.config.ts.
• Prefer CLI-generated services so manifests and generated types stay synchronized.
• Run bunx nuxt-feathers-zod doctor after structural changes.
• Use --dry before write operations on an existing project.