Stuck on prepare after types generated with no error...

[prpanto]

I try to install a nuxt project but it stuck after types generated.... I wait for long but nothing change...

...$ npm i

> postinstall
> nuxt prepare

ℹ Using default Tailwind CSS file                                                                                                                                      nuxt:tailwindcss 10:09:26 AM
✔ Types generated in .nuxt     

[prpanto]

I see the prombel because I have the errors with use of undeclared variable in general I have this error too use of undeclared variable: defineNuxtConfig and that is the reason. But I dont know why what happen with this undeclared error to cause to my project. In another project I dont have the same issue....

[shinGangan]

Hi @prpanto .

Do you know the following environmental information about this issue?
We would appreciate it if you could share this information with us, as the solution may vary depending on the version and environment.

• OS: macOS? Ubuntu? Windows 11?
• Nuxt version
• Node / Bun version
• is exist Error message?
• Other possible influences
  • eg1) Tailwind CSS is used, already set in nuxt.config.ts
  • eg2) I want to use xyz module

[prpanto]

@shinGangan sorry for late reply.
os: ubuntu 22.04
node: v18.17.0
npm: v10.1.0
pnpm: v8.15.4
nuxt: v3.10.*

Today I noticed, the "issue" I face is when I delete the .nuxt, node_modules folders, the package lock file and then I reinstall the app again. Install method just run pnpm or npm install

edit 2: delete .nuxt, node_modules and lock and reinstall (pnpm install) and have the same problem just stuck. i cancel and then pnpm show the installed dependencies. the same problem I have with npm and pnpm.

// package.json

"dependencies": {
    "@iconify/json": "^2.2.188",
    "@nuxt/ui-pro": "^1.0.1",
    "@octokit/core": "^6.0.1",
    "h3": "^1.11.1",
    "h3-zod": "^0.5.3",
    "nuxt": "^3.10.3",
    "nuxt-auth-utils": "^0.0.20",
    "prisma": "^5.10.2",
    "showdown": "^2.1.0",
    "ufo": "^1.4.0",
    "vue": "^3.4.19",
    "vue-router": "^4.3.0",
    "zod": "^3.22.4"
  },
  "devDependencies": {
    "@nuxt/devtools": "^1.0.8",
    "@nuxtjs/fontaine": "^0.4.1",
    "@prisma/client": "^5.10.2",
    "@vueuse/nuxt": "^10.9.0",
    "typescript": "^5.3.3"
  }

// nuxt.config.ts

export default defineNuxtConfig({
  devtools: { enabled: true },
  extends: ['@nuxt/ui-pro'],
  modules: ['@nuxt/ui', '@vueuse/nuxt', 'nuxt-auth-utils', '@nuxtjs/fontaine'],
  ui: {
    icons: ['heroicons', 'simple-icons', 'mdi', 'lucide', 'fluent-mdl2']
  },
  fontMetrics: {
    fonts: [
      {
        family: 'Nasalization',
        src: 'nasaliza.woff' 
      }
    ],
  },
})

[shinGangan]

Hi @prpanto , thanks for the answer.
I thought it would be easier for the maintainer team to guess and answer the question if we had more information about the environment.

I have not observed a similar error on my end, so I am preparing a similar environment to verify the issue. Sorry I can't help you right away. 🙏