You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a Windows only thing (I posted the same issue in the Astro Repo and they already fixed it #8831)
When I'm working with Vite and there are CLI prints in the terminal that mention the path, it prints the entire PC path.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
If you want to, you can use customLogger (https://vitejs.dev/config/shared-options.html#customlogger), following the example shown you can override .warn and .error to strip out any string paths that matches process.cwd() and the normalized version (slashes instead of backslashes). "vite" also exports normalizePath() which you can pass process.cwd() to get the normalized version.
Describe the bug
This might be a Windows only thing (I posted the same issue in the Astro Repo and they already fixed it #8831)
When I'm working with Vite and there are CLI prints in the terminal that mention the path, it prints the entire PC path.
Reproduction
https://stackblitz.com/edit/vitejs-vite-vwvezs?file=index.html
Steps to reproduce
Open a project in windows and make the CLI print your path.
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: