Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nuxt Dev server broken after 2.16.0 update #1773

Closed
tobychidi opened this issue May 10, 2024 · 12 comments
Closed

Nuxt Dev server broken after 2.16.0 update #1773

tobychidi opened this issue May 10, 2024 · 12 comments
Labels
bug Something isn't working needs reproduction

Comments

@tobychidi
Copy link

tobychidi commented May 10, 2024

Environment

  • Operating System: Windows_NT
  • Node Version: v20.13.0
  • Nuxt Version: 3.11.2
  • CLI Version: 3.11.1
  • Nitro Version: 2.9.6
  • Package Manager: pnpm@9.1.0
  • Builder: -
  • User Config: alias, build, experimental, watch, ui, devtools, modules, gtag, runtimeConfig, routeRules, router
  • Runtime Modules: @nuxt/ui@2.15.2, @pinia/nuxt@0.5.1, @nuxt/image@1.7.0, @vueuse/nuxt@10.9.0, nuxt-gtag@2.0.5, @vue-email/nuxt@0.8.19
  • Build Modules: -

Version

v2.16.0

Reproduction

Set this up on CodeSandBox. It is still not running. Reproduction

Description

After the update to the latest versions and I try to run Nuxt dev server, the server crashes and reverting to v2.15.2 resolves the issue. Pls help.

Additional context

No response

Logs

No driver set for storage mount point "50".                                                    nitro 9:15:27 AM


 WARN  No driver set for storage mount point "100".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "200".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "300".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "400".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "500".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "600".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "700".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "800".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "900".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "950".                                                   nitro 9:15:27 AM


 WARN  No driver set for storage mount point "DEFAULT".                                               nitro 9:15:27 AM

ℹ Tailwind Viewer: http://localhost:3000/_tailwind/                                       nuxt:tailwindcss 9:15:27 AM

 ERROR  [uncaughtException] callback is not a function                                                      9:15:28 AM

  at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
@tobychidi tobychidi added the bug Something isn't working label May 10, 2024
Copy link
Member

We won't be able to help without a reproduction.

@tobychidi
Copy link
Author

We won't be able to help without a reproduction.

I have updated the description with a link to a CodeSandBox reproduction. Once I update to the latest versions of Nuxt and UI, the app breaks.

@tobychidi
Copy link
Author

Is no one else having this problem?

@noook
Copy link
Collaborator

noook commented May 14, 2024

Your reproduction has npm and pnpm mixed. According to your issue you are using pnpm and this might have something to do with your node_modules. Try deleting package-lock.json and reinstalling with pnpm, this worked for me: https://codesandbox.io/p/devbox/clever-keldysh-forked-mqp3fr?workspaceId=c9efb319-914c-430c-98b5-2a634e608bca

@noook
Copy link
Collaborator

noook commented May 16, 2024

Can I close this @tobychidi ?

@cull2203
Copy link

cull2203 commented May 18, 2024

Is no one else having this problem?

Yes I have the same issue that started 2 days ago when updating the Nuxt UI version from 2.15.2 to 2.16.0. The error is:
aliases[key].startsWith is not a function

npm will not install anything nor run dev server

@cull2203
Copy link

Your reproduction has npm and pnpm mixed. According to your issue you are using pnpm and this might have something to do with your node_modules. Try deleting package-lock.json and reinstalling with pnpm, this worked for me: https://codesandbox.io/p/devbox/clever-keldysh-forked-mqp3fr?workspaceId=c9efb319-914c-430c-98b5-2a634e608bca

I have tried this and still I am getting errors.

` ERROR aliases[key].startsWith is not a function 9:50:43 AM

at normalizeAliases (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:78102)
at createJITI (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:248943)
at module.exports (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/lib/index.js:14:10)
at loadConfig (node_modules/.pnpm/c12@1.10.0/node_modules/c12/dist/index.mjs:121:34)
at loadOptions (node_modules/.pnpm/nitropack@2.9.6_@opentelemetry+api@1.8.0_encoding@0.1.13/node_modules/nitropack/dist/nitro.mjs:4740:66)
at createNitro (node_modules/.pnpm/nitropack@2.9.6_@opentelemetry+api@1.8.0_encoding@0.1.13/node_modules/nitropack/dist/nitro.mjs:5076:25)
at initNitro (node_modules/.pnpm/nuxt@3.11.2_@opentelemetry+api@1.8.0_@parcel+watcher@2.4.1_@types+node@20.12.12_@unocss+reset_sx4zig6uzirfzdisjdhrh2rtj4/node_modules/nuxt/dist/index.mjs:3366:23)
at async initNuxt (node_modules/.pnpm/nuxt@3.11.2_@opentelemetry+api@1.8.0_@parcel+watcher@2.4.1_@types+node@20.12.12_@unocss+reset_sx4zig6uzirfzdisjdhrh2rtj4/node_modules/nuxt/dist/index.mjs:4270:3)
at async loadNuxt (node_modules/.pnpm/nuxt@3.11.2_@opentelemetry+api@1.8.0_@parcel+watcher@2.4.1_@types+node@20.12.12_@unocss+reset_sx4zig6uzirfzdisjdhrh2rtj4/node_modules/nuxt/dist/index.mjs:4331:5)
at async loadNuxt (node_modules/.pnpm/@nuxt+kit@3.11.2_rollup@4.17.2/node_modules/@nuxt/kit/dist/index.mjs:2570:19)

ERROR aliases[key].startsWith is not a function 9:50:43 AM

 ELIFECYCLE  Command failed with exit code 1.`

@tobychidi
Copy link
Author

Can I close this @tobychidi ?

Not yet. I found that the issue is related with another module @vue-email/nuxt once installed. I have updated the reproduction as well.

@cull2203
Copy link

Can I close this @tobychidi ?

Not yet. I found that the issue is related with another module @vue-email/nuxt once installed. I have updated the reproduction as well.

it looks like I cannot use '@nuxt/ui' and '@vue-email/nuxt' together. However, I did get it to work periodically on '@nuxt/ui': '^2.15.2'. There is another issue raised https://github.com/vue-email/nuxt/issues/45

@kstraszewski
Copy link

I found a workaround for that. You need to change order of nuxt modules, and move Vue-email/nuxt before Nuxt/ui. It fixes this issue for me.

@cull2203
Copy link

I found a workaround for that. You need to change order of nuxt modules, and move Vue-email/nuxt before Nuxt/ui. It fixes this issue for me.

I have tried your solution and it seems to work when updating to @nuxt/ui '^2.16.0'. The problem I found was the previous version.

My modules now look like this and work as expected, thanks for your input.

modules: [ '@vue-email/nuxt', '@nuxt/ui', '@nuxt/image', '@pinia/nuxt', '@pinia-plugin-persistedstate/nuxt', '@nuxtjs/supabase', '@unlok-co/nuxt-stripe', '@nuxtjs/turnstile', 'nuxt-resend', 'nuxt-rating' ]

@Arcadia822
Copy link

I found a workaround for that. You need to change order of nuxt modules, and move Vue-email/nuxt before Nuxt/ui. It fixes this issue for me.

Thanks for the workaround. Fixed instantly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs reproduction
Projects
None yet
Development

No branches or pull requests

6 participants