`changeset` command crashes when default editor is vscode with empty message
See original GitHub issueAffected Packages
Issue with @changesets/cli
Problem
The default editor on my system is vscode
. When running yarn changeset
command I accidentally pressed <kbd>Enter</kbd> without typing any text and it caused my machine to crash.
It kept creating new tabs in the vscode
editor, and even when I quit (multiple times) it created up to 50 new vscode
editor instances. I managed to capture a tiny bit of it before my machine froze.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
`changeset` command crashes when default editor is vscode ...
The default editor on my system is vscode . When running yarn changeset command I accidentally pressed Enter without typing any text and...
Read more >Troubleshoot Terminal launch failures - Visual Studio Code
If your terminal is set to run as administrator only, and you are not launching VS Code as administrator, the terminal will not...
Read more >How can I fix git commit error "Waiting for your editor to close ...
I'm using, or trying it, VS Code as default and I got this same message with it opened or closed. Commits done through...
Read more >Visual Studio 2022 Release Notes | Microsoft Learn
Get the latest features, bug fixes, and support for Visual Studio 2022. Download today.
Read more >a fast and friendly git client for Mac and Windows - Fork
Draft commit message can't be restored sometimes. Fixed. Crash in empty open recent repository dialog. Fixed.
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
@pkieltyka the fix has been published, I hope you’ll give Changesets another chance 😉
We could probably just remove the loop. Not sure why it is needed.