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
yarn install node-gyp errors only with vscode source yarn.lock files #91590
Comments
What are the errors? |
Scrolling through them, it looks like it is for an optional fsevents each time. This warning is followed by a lot of errors from inside fsevents .cc and .h files. I have excluded these due to their length.
I receive similar errors two more times. These are the only differences that I see.
|
It looks like the errors are just related to fsevents which is an optional devDependency. I've had issues building that too, but you can still build vscode without it right? |
Yes, I never noticed the optional part until I was copying the messages. I assume the errors will go away once vscode moves towards whatever newer version the fresh yarn install pulls. This can be closed, unless you want any more information about the versions that install and work. |
Issue Type: Bug
Using yarn install to build vscode throws node-gyp errors when using the yarn.lock files from within the repo. Removing the yarn.lock files and then running yarn install works successfully.
Deleting ~/.node-gyp and running yarn cache clean doesn't seem to make a difference.
This seems to me that when doing yarn install without the lock files, I receive newer versions and this resolves the issue.
If any of the log information is needed, I can provide that.
VS Code version: Code 1.42.1 (c47d83b, 2020-02-11T14:44:27.652Z)
OS version: Darwin x64 19.3.0
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: