-
Notifications
You must be signed in to change notification settings - Fork 4
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
bug: usage with Nuxt 3 in combination with static site generation #24
Comments
Hello @ahoek, I'm not using nuxt at all. The first CSS error looks related to Vuetify, not VPhoneInput. |
Thank you for your quick answer. Both errors do not appear when I'm not using the VPhoneInput component. I'll check further and let it know when I found a solution. |
Thanks. I'm leaving this open because it is not solved. We'll wait for your update, but if there is anything else I can do, let me know. |
I solve with |
You can add dependency in in export default defineNuxtConfig({
...
build: {
transpile: ['v-phone-input']
}
...
}) It should also dedupe vue and reduce bundle size |
Looks like I got some work to do on this if Vue code is duplicated in the package export. Tagging this as a bug. |
After investigating, looks like Vue should correctly be excluded from lib build, thanks to the current lib build configuration. |
I can confirm, that the issue exists. |
Hello everyone having this issue, I'm trying to improve Nuxt support, but this may take a bit of time and testing. I'll keep in touch. |
I'm back. I released npm install v-phone-input@next If everythings good, I will release stable After investigation, this issue had two causes:
You can also try out VPhoneInput+Nuxt inside this Stackblitz playground. |
Closing as it should be fixed in |
Expected Behavior
The component works the same as the non--static-site generated variant
Actual Behavior
The component works correctly in dev mode. When I generate the static site, I'll get the error:
If I add 'v-phone-input' to the "build.transpile" array, the site generates without issue, but I get another error when running via dev :
I don't know if this is an error in the component, or in my configuration
Steps to Reproduce the Problem
See the behavior above.
Specifications
The text was updated successfully, but these errors were encountered: