-
Notifications
You must be signed in to change notification settings - Fork 11
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 typed router nuxtconfig error (since v2.3.0) #66
Comments
Hi! It's weird, are you sure it's related to nuxt-typed-router? |
When I removed nuxt-typed-router it solved the issue yes. I can get you a reproduction later this day :) |
Yep I would love to! I can't reproduce it with any of internal projects. |
https://github.com/ThimoDEV/nuxt3-tailwind-warning-content/tree/nuxt-hydrated-error Don't mind the repo name, I used it for other issues I encountered. This repo has only nuxt and nuxt typed router. After yarn install I get the error |
Hi there! Got the same problem since i upgraded nuxt to last versions (tried with v3.1.* and v3.2) I tried to reproduce it in a stackblitz env, declaring tailwindcss as a modules appears to be ok... that is not the case of nuxt-typed-router. |
Thanks for the repro! I will investigate, but I think It's related to Nuxt types :( |
Have you tried with |
Yes, think so. The issue appears when we upgrade from Btw you're the only one who provide type-safe routing in Nuxt/Vue env. |
Thanks! :D (BTW I have path autocomplete nearly ready for a next version) |
I may have something I will test on the beta channel |
Ok you can test with |
I just tried it with the latest nuxt version and the latest nuxt typed router release and its working on my end. Thanks for the quick fix! <3 |
Since version 2.3.0 I get the following error in my nuxt config:
Type instantiation is excessively deep and possibly infinite
I used nuxt v3.1.2 for this. It also happened in version 3.1.1
The text was updated successfully, but these errors were encountered: