\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[unhandledRejection] TypeError: dayjs.duration is not a function\n```",[3056,3057],{"name":3046,"color":3047},{"name":3058,"color":3059},"needs reproduction","FBCA04",31759,"Nuxt 3.16.2 does not install settings from the module","2025-04-11T07:53:27Z","https://github.com/nuxt/nuxt/issues/31759",0.7007366,{"description":3066,"labels":3067,"number":3076,"owner":3036,"repository":3036,"state":3077,"title":3078,"updated_at":3079,"url":3080,"score":3081},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v22.7.0\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: yarn@4.4.1\r\n- Builder: -\r\n- User Config: compatibilityDate\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\n```bash\r\nyarn set version stable\r\necho 'nodeLinker: node-modules' > .yarnrc.yml\r\nyarn add nuxt\r\ncat \u003C\u003C'EOF' > nuxt.config.ts\r\nexport default defineNuxtConfig({\r\n compatibilityDate: '2024-09-01'\r\n});\r\nEOF\r\nyarn nuxt dev\r\n```\r\nstart another shell:\r\n```bash\r\nmv nuxt.config.ts{,.bak}; sleep 5; mv nuxt.config.ts{.bak,}\r\n```\r\n\r\n### Describe the bug\r\n\r\n`nuxt dev` will asking me whether to set `compatibilityDate` when it noticed it's not set (or file `nuxt.config.ts` is missing), but it will keep existing after `nuxt.config.ts` is recreated.\r\nThis will affect some remote file synchronizer which will delete or empty the file being upload.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\n$ yarn nuxt dev\r\nNuxt 3.13.0 with Nitro 2.9.7 1:47:47 PM\r\n 1:47:48 PM\r\n ➜ Local: http://localhost:3000/\r\n ➜ Network: use --host to expose\r\n\r\n ➜ DevTools: press Shift + Alt + D in the browser (v1.4.1) 1:47:50 PM\r\n\r\n✔ Vite client built in 48ms 1:47:51 PM\r\n✔ Vite server built in 728ms 1:47:52 PM\r\n✔ Nuxt Nitro server built in 673 ms nitro 1:47:53 PM\r\nℹ Vite client warmed up in 1ms 1:47:53 PM\r\nℹ Vite server warmed up in 1116ms 1:47:54 PM\r\nℹ nuxt.config.ts updated. Restarting Nuxt... 1:47:56 PM\r\n ➜ DevTools: press Shift + Alt + D in the browser (v1.4.1) 1:47:56 PM\r\n\r\n✔ Vite client built in 12ms 1:47:56 PM\r\n✔ Vite server built in 359ms 1:47:57 PM\r\n✔ Nuxt Nitro server built in 508 ms nitro 1:47:57 PM\r\n[1:47:57 PM] ℹ Nuxt now supports pinning the behavior of provider and deployment presets with a compatibility date. We recommend you specify a compatibilityDate in your nuxt.config file, or set an environment variable, such as COMPATIBILITY_DATE=2024-09-01.\r\nℹ Vite client warmed up in 1ms 1:47:57 PM\r\n\r\n❯ Do you want to update your nuxt.config to set compatibilityDate: '2024-09-01'?\r\n● Yes / ○ No\r\n\r\nℹ Vite server warmed up in 1094ms 1:47:58 PM\r\nℹ nuxt.config.ts updated. Restarting Nuxt... 1:48:01 PM\r\n ➜ DevTools: press Shift + Alt + D in the browser (v1.4.1) 1:48:01 PM\r\n\r\n✔ Vite client built in 20ms 1:48:01 PM\r\n✔ Vite server built in 853ms 1:48:02 PM\r\n✔ Do you want to update your nuxt.config to set compatibilityDate: '2024-09-01'?\r\nNo\r\nUsing 2024-04-03 as fallback compatibility date. 1:48:09 PM\r\n```\r\n",[3068,3071,3072,3075],{"name":3069,"color":3070},"good first issue","fbca04",{"name":3027,"color":3028},{"name":3073,"color":3074},"bug","d73a4a",{"name":3030,"color":3031},28776,"closed","`compatibilityDate` prompt preserve after `nuxt.config.ts` get removed and recreated","2024-09-03T10:52:58Z","https://github.com/nuxt/nuxt/issues/28776",0.58830667,{"description":3083,"labels":3084,"number":3093,"owner":3036,"repository":3036,"state":3077,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.13.1`\n- Nuxt Version: `3.15.3`\n- CLI Version: `3.20.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `ssr`, `spaLoadingTemplate`, `modules`, `runtimeConfig`, `css`, `vite`, `googleFonts`, `vue`, `devtools`\n- Runtime Modules: `@nuxtjs/google-fonts@3.2.0`, `@nuxtjs/tailwindcss@6.13.1`, `floating-vue/nuxt@5.2.2`, `nuxt-icons@3.2.1`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://github.com/frederik-station/nuxt-netlify\n\n### Describe the bug\n\nI updated my SPA app from Nuxt 3.6.5 to 3.15.3 and ran `nuxt dev`. I then got asked by the script \"Do you want to update your nuxt.config to set compatibilityDate: '2025-01-27'?\". After accepting and deploying to Netlify my build ran through without error but upon visiting my app I got an HTTP 500 error.\n\nIn the build logs I see:\n[info] [nitro] Building Nuxt Nitro server (preset: `netlify`, compatibility date: `2025-01-27`)\n\nAfter removing the compatibilityDate from nuxt.config.ts and redeploying my app is working again and I get the following log message:\n[info] [nitro] Building Nuxt Nitro server (preset: `netlify-legacy`, compatibility date: `2024-04-03`)\n\nWhy is my app not working with the 'netlify' preset?\nI don't really get the concept of this compatibility date. Why is Netlify selecting a different preset based on the compatibility date? How am I supposed to figure out the correct compatibilityDate?\n\n### Additional context\n\n**Netlify Deploy Settings**\nBuild command: npm run build\nPublish directory: dist\nNode 22\n\n**Nuxt Config**\n```\nexport default defineNuxtConfig({\n ssr: false,\n spaLoadingTemplate: false,\n\n modules: [\n '@nuxtjs/google-fonts',\n '@nuxtjs/tailwindcss',\n 'floating-vue/nuxt',\n 'nuxt-icons',\n ],\n\n css: ['~/assets/css/main.scss'],\n\n vite: {\n css: {\n preprocessorOptions: {\n scss: {\n additionalData: '@import \"@/assets/css/mixins\";',\n },\n },\n },\n },\n\n googleFonts: {\n families: {\n Arimo: true,\n Baskerville: true,\n },\n },\n\n vue: {\n compilerOptions: {\n isCustomElement: (tag) => tag === 'lottie-player',\n },\n },\n\n devtools: {\n enabled: true,\n },\n});\n```\n\n\n### Logs\n\n```shell-script\n\n```",[3085,3086,3089,3090],{"name":3046,"color":3047},{"name":3087,"color":3088},"nitro","bfd4f2",{"name":3058,"color":3059},{"name":3091,"color":3092},"possible regression","B90A42",30789,"Netlify build breaks due to compatibilityDate","2025-03-18T22:29:20Z","https://github.com/nuxt/nuxt/issues/30789",0.628687,{"description":3099,"labels":3100,"number":3102,"owner":3036,"repository":3036,"state":3077,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Environment\n\nWorking directory: /Users/stephenjasonwang/Development/test123 \r\nNuxt project info: (copied to clipboard) \r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v22.6.0\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.26\r\n- Builder: -\r\n- User Config: compatibilityDate, future, modules, devtools\r\n- Runtime Modules: @vueuse/nuxt@10.11.1\r\n- Build Modules: -\r\n------------------------------\r\n\r\n \r\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new?template=bug-report.yml\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n👉 Read documentation: https://nuxt.com\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-3-vueuse-motion-pmteh2?file=client%2Fapp.vue\n\n### Describe the bug\n\nWithout compatibility 4\r\n\u003Cimg width=\"596\" alt=\"image\" src=\"https://github.com/user-attachments/assets/3c8ee497-4dca-46af-a410-47524d15b1f7\">\r\n\r\n\r\nWith compatibility 4\r\n\u003Cimg width=\"1029\" alt=\"image\" src=\"https://github.com/user-attachments/assets/1110c9ec-0bf9-4b00-8cc4-893910db9bf3\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3101],{"name":3046,"color":3047},28694," future: { compatibilityVersion: 4 } Messes up some types","2024-08-24T16:56:09Z","https://github.com/nuxt/nuxt/issues/28694",0.6689266,{"description":3108,"labels":3109,"number":3111,"owner":3036,"repository":3036,"state":3077,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v22.3.0\r\n- Nuxt Version: 4.0.0-28664444.6bb24c14\r\n- CLI Version: 3.13.0-1719571044.bca75ab\r\n- Nitro Version: -\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: devtools, future, compatibilityDate\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-u2t8fv?file=nuxt.config.ts\n\n### Describe the bug\n\nSimply create a new nuxt project and follow the instruction to test the V4.\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n$ nuxt prepare\r\n[11:52:45 PM] ℹ Nuxt now supports pinning the behavior of provider and deployment presets with a compatibility date. We recommend you specify a compatibilityDate in your nuxt.config file.\r\nUsing 2024-04-03 as fallback compatibility date. 11:52:45 PM\r\n\r\n[11:52:45 PM] WARN [nuxt] Expected @nuxt/kit to be at least 4.0.0-28664444.6bb24c14 but got 3.12.2. This might lead to unexpected behavior. Check your package.json or refresh your lockfile.\r\n\r\n\r\n[11:52:45 PM] WARN [nuxt] Expected @nuxt/schema to be at least 4.0.0-28664444.6bb24c14 but got 3.12.2. This might lead to unexpected behavior. Check your package.json or refresh your lockfile.\r\n\r\nℹ Running with compatibility version 4 11:52:46 PM\r\n\r\n ERROR Cannot read properties of undefined (reading 'bind') 11:52:46 PM\r\n\r\n at loadNuxt (node_modules/@nuxt/kit/dist/index.mjs:2749:56)\r\n at async Object.run (node_modules/nuxi/dist/chunks/prepare.mjs:76:18)\r\n at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi-nightly.618a108a.mjs:1680:16)\r\n at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi-nightly.618a108a.mjs:1671:11)\r\n at async runMain$1 (node_modules/nuxi/dist/shared/nuxi-nightly.618a108a.mjs:1809:7) \r\n\r\n\r\n\r\n ERROR Cannot read properties of undefined (reading 'bind') 11:52:46 PM\r\n\r\nerror Command failed with exit code 1.\r\ninfo Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.\n```\n",[3110],{"name":3046,"color":3047},27956,"V4 - Cannot read properties of undefined (reading 'bind') - @nuxt/kit","2024-07-01T22:00:37Z","https://github.com/nuxt/nuxt/issues/27956",0.67931074,{"description":3117,"labels":3118,"number":3122,"owner":3036,"repository":3036,"state":3077,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.16.0`\r\n- Nuxt Version: `3.12.2`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.6`\r\n- Package Manager: `pnpm@9.9.0`\r\n- Builder: `-`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/app-config-bug\r\n(The reproduction is in Nuxt `v3.13.0`, but the bug also occurs in `v3.12`)\r\n\r\n### Describe the bug\r\n\r\nWhen calling `updateAppConfig()` and passing a `RegExp` or a `Date`, these values doesn't work as expected:\r\n- If the value already exists, it won't be updated and always keeps the previous value.\r\n- If the value doesn't exist, it will be initialized as an empty object `{}`.\r\n\r\n```js\r\n// app.config.ts\r\nexport default defineAppConfig({\r\n regExp: /foo/i,\r\n date: new Date(1111, 11, 11),\r\n});\r\n\r\n// app.vue\r\nupdateAppConfig({\r\n // These existing values won't be updated at all\r\n regExp: /bar-updated/g,\r\n date: new Date(2222, 12, 12),\r\n\r\n // These new values will just be init as an empty object `{}`\r\n regExpNew: /bar-updated/g,\r\n dateNew: new Date(2222, 12, 12),\r\n});\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3119,3120],{"name":3073,"color":3074},{"name":3121,"color":3059},"🔨 p3-minor",28772,"`updateAppConfig()` doesn't work as expected for values like `RegExp` and `Date`","2024-09-02T11:12:59Z","https://github.com/nuxt/nuxt/issues/28772",0.68053913,{"description":3128,"labels":3129,"number":3131,"owner":3036,"repository":3036,"state":3077,"title":3132,"updated_at":3133,"url":3134,"score":3135},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v20.15.0\r\n- Nuxt Version: 3.12.3\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.7.0\r\n- Builder: -\r\n- User Config: future, devtools, components\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\n1. Run `npx nuxi@latest init --package-manager npm nuxt-config-formatting-repro`.\r\n2. Modify `nuxt.config.ts` to give it more \"depth\"\r\n3. Run `npm run dev`\r\n4. Accept the suggested compatibilityDate\r\n5. View the newly modified `nuxt.config.ts`\r\n\r\nExample repo here: https://github.com/minimusubi/nuxt-config-formatting-repro\r\nA diff of nuxt.config.ts before and after nuxt modifies it: https://github.com/minimusubi/nuxt-config-formatting-repro/compare/e1d42f089e44d42d30a1a0b27ef5c160f69deba2...fb1ae3af952a35e7a4fddac3a5aedaacc8ad2bb0\n\n### Describe the bug\n\n### Expected outcome\r\nAfter nuxt modifies `nuxt.config.ts`,\r\n\r\n- The file should be formatted similarly to how it was before\r\n- OR, at the very minimum\r\n- The file should be formatted consistently, even if it differs from previous formatting\r\n - Meaning,\r\n - If it's going to use spaces, use them. Always. 2 spaces? 4 spaces? It doesn't really matter, as long as it sticks to it.\r\n - If it's going to use tabs, use them. Don't use both.\r\n - Indentation should make sense.\r\n\r\nAlternatively,\r\n\r\n- Don't attempt to format the file\r\n\r\n### Actual outcome\r\nNuxt applies very odd indentation to `nuxt.config.ts`. Note that some lines use a wild number of tabs, and some lines use just a single (!) space.\r\n\r\nExample of a nuxt-modified config:\r\n```js\r\n// https://nuxt.com/docs/api/configuration/nuxt-config\r\nexport default defineNuxtConfig({\r\n future: {\r\n\t\t\t\t\tcompatibilityVersion: 4,\r\n\t},\r\n\r\n devtools: { enabled: false },\r\n\r\n // https://nuxt.com/docs/api/nuxt-config#components\r\n\tcomponents: [\r\n\t\t\t\t\t{\r\n\t\t\t\t\t\t\t\t\tpath: '~/components/global',\r\n\t\t\t\t\t\t\t\t\tglobal: true,\r\n\t\t\t\t\t},\r\n\t\t\t\t\t'~/components',\r\n\t\t\t\t\t// This line is custom\r\n\t\t\t\t\t// https://github.com/nuxt/nuxt/discussions/17167#discussioncomment-3288741\r\n\t\t\t\t\t{ path: '~/components/common', pathPrefix: false },\r\n\t],\r\n\r\n compatibilityDate: '2024-07-04',\r\n});\r\n```\n\n### Additional context\n\nWith further inspection, it seems that\r\n\r\n- Whenever nuxt indents a line using tabs, it seems to (correctly) use a single tab for the first indent level, but then uses 4 tabs per indent level for each level after.\r\n- Whenever it used spaces, it only used one space.\r\n\r\nMaybe, it used spaces where it should have used tabs, and tabs where it should have used spaces?\r\nThis analysis was only conducted with the example config given. I didn't explore adding more config options.\n\n### Logs\n\n_No response_",[3130],{"name":3046,"color":3047},28038,"Nonsensical formatting for nuxt.config.ts when accepting suggested compatibilityDate","2024-07-05T10:06:53Z","https://github.com/nuxt/nuxt/issues/28038",0.6821357,{"description":3137,"labels":3138,"number":3147,"owner":3036,"repository":3036,"state":3077,"title":3148,"updated_at":3149,"url":3150,"score":3151},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.18.1`\r\n- Nuxt Version: `2.15.0`\r\n- Nitro Version: `2.3.3`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `webpack`\r\n- User Config: `pages`, `build`, `css`, `plugins`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\n **don't have a minimal reproduction link but the issue is pretty self explanatory!\r\nThis is my package.json:**\r\n`\r\n{\r\n \"name\": \"nuxt-app\",\r\n \"private\": true,\r\n \"scripts\": {\r\n \"build\": \"nuxt build\",\r\n \"dev\": \"nuxt dev\",\r\n \"generate\": \"nuxt generate\",\r\n \"preview\": \"nuxt preview\",\r\n \"postinstall\": \"nuxt prepare\"\r\n },\r\n \"devDependencies\": {\r\n \"@types/node\": \"^18\",\r\n \"nuxt\": \"^3.4.1\"\r\n }\r\n}\r\n`\r\nand you see my environment above which display different nuxt versions!\n\n### Describe the bug\n\nI create a nuxt app by running `npx nuxi init [project-name]`. When the project is created I see `\"nuxt\": \"^3.4.1\",` in my package.json. But as you can see in my environment when I run `npx nuxi info` it says my nuxt version is `Nuxt Version: 2.15.0` which makes me a lot of problems such as getting the error `defineNuxtConfig is not defined` is not defined in my `nuxt.config.ts`\r\nWhat is wrong here?\n\n### Additional context\n\nMy application is pretty empty since it was created brand new but just in case this is my tsconfig.json:\r\n`{\r\n // https://nuxt.com/docs/guide/concepts/typescript\r\n \"extends\": \"./.nuxt/tsconfig.json\"\r\n}\r\n`\r\n\r\n\n\n### Logs\n\n_No response_",[3139,3142,3145,3146],{"name":3140,"color":3141},"types","2875C3",{"name":3143,"color":3144},"3.x","29bc7f",{"name":3046,"color":3047},{"name":3058,"color":3059},20377,"defineNuxtConfig is not defined ","2024-10-28T14:00:52Z","https://github.com/nuxt/nuxt/issues/20377",0.68618417,["Reactive",3153],{},["Set"],["ShallowReactive",3156],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9p7CsZRsr061htetf6IsRUrSW-O7eDhbxtUQVhT4fm4":-1},"/nuxt/nuxt/28021"]