-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
v3 import()
and v2 import()
behavior is inconsistent
#9265
Comments
At least, this should show warning (Variable imports cannot import their own directory) or work. |
Agreed, I would prefer it to work😜. |
Same Problem. I reverse vite to v2 now. |
|
I have the same issue that I ran into |
I found this plugin https://github.com/vite-plugin/vite-plugin-dynamic-import#readme it works for me but not sure if it breaks anything else. Preferably this bug should be fixed since it looks to me like a regression. |
Same error with ../ import in Vite3. |
@ahnpnl adding this plugin did the trick, good workaround for now :-) |
Describe the bug
Related issues: #9179
Describe
The final path is
../components/Com1.vue
, but glob result is missing../components
. This is valid invite2
.I don't know if this is a
break changes
or abug
, and I don't see any documentation mentioning it.Reproduction
https://stackblitz.com/edit/vitejs-vite-mtfend?file=src/components/Test.vue
System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: