Skip to content

fix(driver): crash with VSCode debug terminal #405

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

Conversation

mxschmitt
Copy link
Member

@mxschmitt mxschmitt commented Dec 27, 2020

Visual Studio Code sets In their JavaScript Debug Terminal the NODE_OPTIONS env var with debugging arguments. But vercel/pkg - the driver can't deal with that and exists directly with a weird error message which results that the library is not working. Users either use it and will face into that and wondering what is happening or they are randomly using that terminal.

It should also be applied to Java, C#, and Go but for them its probably not that a high chance that a VSCode user will this kind of special terminal (debug terminal). I used it unintentionally a few months ago if you remember, so makes probably sense to fix it in all the language providers.
Unfortunately we can't fix it on the driver side afaik.

Contains also some other smaller drive-by nits.

@pavelfeldman pavelfeldman merged commit 0b4a980 into microsoft:master Dec 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants