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
{{ message }}
Repository navigation
[vite plugin] [command shift click to open in editor] [macos + vs code] -> make sure you can run "code" from the terminal #418
If command shift click (meta shift click) to open in editor does not work on macos with vscode:
In vs code:
Shift + Command + P
type install 'code' Shell command in PATH.
open a new terminal and run code . to check that it works (it should open vscode in your current directory).
Now you can command shift click from the browser and it open in editor.
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
Screenshots or Videos (Optional)
Do you intend to try to help solve this bug with your own PR?
Yes, I think I know how to fix it and will discuss it in the comments of this issue
Terms & Code of Conduct
I agree to follow this project's Code of Conduct
I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
Thanks for the report. To make this actionable, could you add a minimal reproducible example link (CodeSandbox, StackBlitz, or a small public repo) that demonstrates the failing behavior on macOS + VS Code before the workaround? The required repro field is currently empty, and without a runnable repro it’s hard to verify and debug. It would also help to include the expected behavior vs. actual behavior in that repro.
changed the title [-][vite plugin command shift click to open in editor] [macos + vs code] -> make sure you have Shell command 'code' successfully installed in PATH.[/-][+][vite plugin ] [command shift click to open in editor] [macos + vs code] -> make sure you can run "code" from the terminal[/+]on Apr 7, 2026
changed the title [-][vite plugin ] [command shift click to open in editor] [macos + vs code] -> make sure you can run "code" from the terminal[/-][+][vite plugin] [command shift click to open in editor] [macos + vs code] -> make sure you can run "code" from the terminal[/+]on Apr 9, 2026
Activity
github-actions commentedon Apr 7, 2026
Thanks for the report. To make this actionable, could you add a minimal reproducible example link (CodeSandbox, StackBlitz, or a small public repo) that demonstrates the failing behavior on macOS + VS Code before the workaround? The required repro field is currently empty, and without a runnable repro it’s hard to verify and debug. It would also help to include the expected behavior vs. actual behavior in that repro.
[-][vite plugin command shift click to open in editor] [macos + vs code] -> make sure you have Shell command 'code' successfully installed in PATH.[/-][+][vite plugin ] [command shift click to open in editor] [macos + vs code] -> make sure you can run "code" from the terminal[/+][-][vite plugin ] [command shift click to open in editor] [macos + vs code] -> make sure you can run "code" from the terminal[/-][+][vite plugin] [command shift click to open in editor] [macos + vs code] -> make sure you can run "code" from the terminal[/+]