-
Notifications
You must be signed in to change notification settings - Fork 31
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
Extension host stops in VSCODE #104
Comments
Maybe related to this: microsoft/vscode#68024 |
As per mentions bug link, i downgraded to vscode 1.30 and it seems to work again. |
thank you for finding this out and reporting it here, I was not aware of it. I have subscribed to the issue and will follow the discussion. |
I can confirm Tim's report. The problem started to occur with one of the last updates of VS code.
|
The same issue has been observed and fixed here: ritwickdey/vscode-live-server#250 Looks like it's caused by the Electron and NodeJS updates in 1.31 (and above), which is why downgrading to 1.30.2 fixes the issue. Judging by ritwickdey/vscode-live-server#267, ritwickdey/vscode-live-server@ca594e4 seems to fix this issue. |
Thanks for the help! So it seems updating Chokidar/fsevents will fix this. I had planned to work on Argdown this week anyway so you won't have to wait long for the next release. |
Same issue with Version 1.32.3 (1.32.3) |
Hi, thanks for the notification, I have just tested this myself. I did update chokidar in the last release (which depends on fsevents), but apparently Chokidar has updated fsevents to the new napi version in 3.0.0-pre but this is not released yet. Not sure what to do right now. |
@hevisko can you please go to your VSCode told me that it had updated the extension, but the error message was still coming from the old version. So I guess there was something wrong with the update process. |
I get this error message in the developer console when opening an argdown file in VSCode, or trying to visualize one.
Is this a known error? Or maybe related to other VSCode plugins?
The text was updated successfully, but these errors were encountered: