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
The object notation for aliases is not functioning properly. #3822
Comments
Please share a repo or a stackblitz demo (https://vitepress.new) where we can verify this. Most likely the paths are not resolving properly in first case. Have you tried using |
Sure. I created demo project where I import |
Sorry, it should be Based on usage it seems that's how one is supposed to use them - https://github.com/search?q=vite%20alias%20/%5B'%22%5D%5B@~%5D.*?%5B'%22%5D:%20%5B'%22%5D%5C//&type=code Might be better to create docs PR to rollup make it more clear. |
Describe the bug
I'm trying to connect Laravel's structure with Vitepress subfolder via Vite aliases. It works properly when using
fileURLToPath(new URL('./path', import.meta.url))
to wrap the path, but it doesn't work with the simplified object notation.Reproduction
Vitepress config file:
Expected behavior
As described in ViteJS docs:
If I haven't missed something, the configuration should work as follows:
System Info
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: