Won't run on Windows in folder 'drag&drop'
See original GitHub issueDescribe the bug
Vite won’t run on Win10 in the folder with the name drag&drop
(both dev/build)
Probably since Vite 1.x - https://github.com/vitejs/vite/issues/582
Logs
Translation: "drop\node_modules.bin" - is not internal or external command, executable program, or batch file.
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (10 by maintainers)
Top Results From Across the Web
Can't Drag And Drop Things in Windows 10? Here's How to ...
In File Explorer, click any file or folder and hold the left button on your mouse. Then, press the Esc key. Now, try...
Read more >How to Fix Not Working Drag and Drop Function on Windows ...
Restart the File Explorer to fix drag and drop not working on Windows 10 · Open Windows Task Manager (press Ctrl + Alt...
Read more >Fix problem: Drag and drop not working in Windows
When drag and drop does not work, left-click a file in File Explorer and keep the left click mouse button pressed. While the...
Read more >Drag and Drop Not Working in Windows 10/11 PC Fix
Step 1: Go to the file or folder on your desktop that you want to drag, left-click on it. Step 2: While holding...
Read more >drag and drop stopped working - Microsoft Community
When drag and drop doesn't work, left click a file in Windows Explorer or File Explorer, and keep the left click mouse button...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, was doing the same testing. Projects created with yarn work fine. (npm run dev, yarn dev both work) Projects created with npm won’t run on both npm/yarn.
It seems that the issue only occurs on npm, and does not occur on yarn nor pnpm, though the latter outputs some strange warnings.