-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
install-extension command throws Buffer deprecated warning #82524
Comments
1.40.2 still has this error as well when installing following extensions: formulahendry.code-runner, formulahendry.auto-close-tag, formulahendry.dotnet-test-explorer, formulahendry.docker-explorer, vsciot-vscode.azure-iot-tools, vsciot-vscode.azure-iot-edge, eamodio.gitlens, and a few others. It does appear to be a built-in problem within vscode when installing extensions via cli. |
I am not able to see these warning when running from sources. Also I have not changed any node dependencies from 1.36. I was clue less from where these warnings are coming from. Any help would be appreciated. |
@sandy081 maybe try this:
From now on you should see stacktraces where the offender is coming from. Alternatively, if we know the extension that is causing this, try to find the deprecated usages of the Buffer constructor. |
Tried this |
|
Yes running out of source did not work. Tried on insiders and I can see the error now. Thanks. |
This is coming from |
am having the same issue but on usage ex.https://github.com/fabiospampinato/vscode-open-multiple-files however it show on first run only. |
It appears on On Sigh... |
That's a good idea. Will look into that.
Thanks, added upstream-issue-linked label |
I am trying to install 23 extensions so that I have similar work environments without VPN (Windows) and with VPN (Linux). I have observed that all 23 extensions install fine on Windows with
But I can only install 3 extensions on Linux with
|
@jdstraye your issue is unlikely to be related to this one. More likely the extensions require a more recent version of VS Code than the 1.63.2 your Linux environment has. |
@gjsjohnmurray, |
@jdstraye AFAIK the deprecation warning is only a warning, and only appears when installing using the CLI or when developing extensions. I wouldn't expect any extension to fail because of it. More likely the latest versions of some extension won't install on your older VS Code version. |
Sure, but what if you're in an enterprise environment and want to push out Visual Studio Code + XYZ extensions to 100s or 1000s of workstations and regularly update said extensions. From memory, the warning output also pauses the installation of extensions until the user inputs any key into the console window.... All I want is the ability to install extensions via CLI without errors/warnings/additional console windows popping up. That's hardly an unreasonable request. |
Is it possible that this warning is happening only when you have |
Issue detected again in the following version:
Here are the Windows Terminal traces of my script executing the command:
|
Same as above:
|
On Windows:
|
Issue Type: Bug
I have verified that the warning does NOT occur in version 1.36.0 in which similar issue #67534 was fixed.
VS Code version: Code 1.39.0 (9df03c6, 2019-10-09T06:58:04.439Z)
OS version: Windows_NT x64 10.0.19500
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_deferred_display_list: disabled_off
skia_renderer: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: disabled_off
webgl: enabled
webgl2: enabled
Extensions (5)
The text was updated successfully, but these errors were encountered: