Typescript: Development HMR option returns error in 3.8.0

[BenjaminOddou]

Hello,

since I updated to 3.8.0 I have an error in my nuxt.config.ts file :

Object literal may only specify known properties, and 'port' does not exist in type '{ enabled?: boolean | undefined; }'.ts(2353)
(property) port: number

export default defineNuxtConfig({
  content: {
    watch: {
      port: 3000,
      https: {
        key: './certs/localhost-key.pem',
        cert: './certs/localhost.pem',
      },
    },
  },

from node_modules/@nuxt/content/dist/module.d.mts I can see :

    /**
     * Development HMR
     * @default { enabled: true }
     */
    watch?: {
        enabled?: boolean;
    };

------------------------------
- Operating System: Linux
- Node Version:     v24.6.0
- Nuxt Version:     4.1.3
- CLI Version:      3.29.1
- Nitro Version:    2.12.6
- Package Manager:  npm@11.6.2
- Builder:          -
- User Config:      compatibilityDate, site, modules, supabase, devtools, css, content, vite, icon, devServer, routeRules
- Runtime Modules:  @nuxt/image@2.0.0, @nuxt/ui@4.1.0, @nuxt/content@3.8.0, nuxt-og-image@5.1.12, @nuxtjs/supabase@2.0.1, @pinia/nuxt@0.11.3, pinia-plugin-persistedstate/nuxt@4.7.1
- Build Modules:    -
------------------------------

[dargmuesli]

I think you can simply remove the custom watch configuration as nuxt content now uses the same Vite dev server as Nuxt: #3546

[farnabaz]

Oh, nice catch. I forgot to update the docs.

In 3.8 Content does not rely on it's own websocket and uses Vite's websocket to handle Hot reload. Consider removing content.watch options.
Please provide a reproduction repository if issue persists.