-
Notifications
You must be signed in to change notification settings - Fork 131
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 missing deps #1783
Comments
Oh this was definitely fixed... Hmm Ill take a look |
I have to confirm this... for me it's breaking for |
@amritk @marclave still not working on 0.0.54 https://codesandbox.io/p/devbox/nuxt-playground-forked-32ms33 |
thanks @laylatichy ! was automatically closed with the reference. @amritk lets take a look at this? : ) |
Yep taking a look now, so this exact error was fixed but it seems its come back |
Alright this specific issue should be fixed in #1843, there's a couple more minor things to fix but this should get nuxt working! |
Hi @laylatichy were you using
What currently does not work is pnpm without |
indeed seems to work with hoist on pnpm now, thank you |
@amritk sorry to ping you, but as You are on the nuxt integration I think maybe You can help with it setting pathRouting basePath to '/' causes all side menus to ignore the domain https://codesandbox.io/p/devbox/nuxt-playground-forked-32ms33 with anything else like '/xxxxx' url in the side menu is generated fine, is it like that by design or something to fix? |
hey @laylatichy mind opening a new ticket for that? then we can close this one and it'll be easier to track |
Closing this ticket as completed |
What happens?
Just tried setting up nuxt scalar since you introduced multiple api specs but it keeps crashing with missing deps
What did you expect to happen?
working demo ;)
How can we reproduce the issue?
https://codesandbox.io/p/devbox/nuxt-playground-forked-32ms33
once the hydration kicks in You will see 500 error
first I thought it might be related to pnpm modules resolution so tried shameful hoisting, then tried npm, yarn but still the same
Swagger/OpenAPI Example
No response
The text was updated successfully, but these errors were encountered: