-
Notifications
You must be signed in to change notification settings - Fork 1
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
Typescript error on nuxt #9
Comments
Hey again, Saw that you acted quickly on this, unfortunately it appears as that was not the cause https://stackblitz.com/edit/nuxt-starter-1zj34w?file=package.json,nuxt.config.ts,pages%2Ftest.vue I'm not too used to typescript or module/package releases so can't really help much more and have no idea what could be causing this. It's also not really a bother for us to add typescript as a top level dep, it's just that this is the first module that requires it, and we're using about 20 modules. Cheers, thanks again for releasing this ❤️ |
@ptdev Hi, i'm still working on this issue. Typescript should not be in dependencies, i tried to add it to devDependencies but it seems to not working. I can reproduce this too with a fresh install, thanks you for you reproduction anyway. |
Hi, finally i had to add it to dependencies, i don't know exactly why but
I will make an issue on nuxt module official github to find why. |
Hi,
We have just tried installing this module on a nuxt 3 app, but when trying to access a page with the component we get the following error:
Installation was done according to the documentation:
Note that we are using nuxt with typescript (<script setup lang="ts">) although we did not explicitly install "typescript" on our app with npm or yarn.
But if we do add typescript manually, then the issue with this module goes away, so I'm guessing it's just an issue of this module's package.json not referencing typescript on its dependencies, so users are forced to add it manually on their apps, which is not common and should probably be fixed.
Thank you, cheers 👍
The text was updated successfully, but these errors were encountered: