-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Forms: Incorrect main/module/exports error when importing #6709
Comments
same here |
Thanks a lot for your report! I'll check and get back to you. |
Wanted to try out this new form stuff and got hit with this massive blocker. |
PrimeVue 4.2.1 Released 🚀 Please try it. |
That fixed it, thank you for the quick release. |
I getting a similar error for the yup resolver: "[plugin:vite:import-analysis] Failed to resolve import "@primevue/forms/resolvers" from "". Does the file exist?" |
@mertsincan Importing the yupResolver by pointing to the yup sub-folder works, though the IDE shows an error So it looks like the resolver isn't being passed up to the top level exports from the resolvers library. |
Thanks a lot for your update! Could you please create a new ticket for it? Feel free to share any more feedback, I'd really love to hear that! |
Describe the bug
Vite reports an error when trying to find the @primevue/forms package.
The Vite error is "[vite] Internal server error: Failed to resolve entry for package "@primevue/forms". The package may have incorrect main/module/exports specified in its package.json."
My own package.json has type="module" listed.
Maybe one of the errors listed in this linter is causing the problem: https://publint.dev/@primevue/[email protected]
Reproducer
https://stackblitz.com/edit/primevue-4-vite-issue-template-v4gdpp?file=src%2FApp.vue
PrimeVue version
4.2.0
Vue version
4.x
Language
ES6
Build / Runtime
Vite
Browser(s)
No response
Steps to reproduce the behavior
Add @primevue/forms to a project. Import from the library.
Expected behavior
No response
The text was updated successfully, but these errors were encountered: