You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with powertoys file locksmith I can see that the file is locked when the extension is enabled. npm ci runs successful again after ending the process or disabling the extension.
As explained in #1421 the eslint server is kept alive for performance reasons when VS Code is running. If Node iself or one of its modules keeps a lock on these files there is little I can do as a developer of the extension.
I will close the issue since I have no plans to implement a mode that supports process spawning.
Type: Bug
same as #1421 but with
npm ci
in an nx workspace.with powertoys file locksmith I can see that the file is locked when the extension is enabled.
npm ci
runs successful again after ending the process or disabling the extension.related issues I could find:
nrwl/nx-console#1863
Extension version: 2.4.4
VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.22631
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: