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
I installed this extension into VS Code-Insiders and like it. I found out recently when working on an Electron project that it seems to prevent modification or deletion of asar archive files (reference electron/electron#6295, particularly @bpasero's comments as it directly relates to VS Code extensions, for details).
I suspect that there is a resource lock happening when reading from or writing to .asar files from this extension when it has it "open" in the UI. In this case, I don't really want the asar files to be read from; I just want to be able to run the build process without having to disable the extension or close Code.
I'm also not surprised if this is a Windows-only issue, as I know that they are particular about how FS transactions work, though I also wouldn't be surprised if other platforms have a similar problem.
Until this issue is rectified, however, I will have to disable this extension.
The text was updated successfully, but these errors were encountered:
I installed this extension into VS Code-Insiders and like it. I found out recently when working on an Electron project that it seems to prevent modification or deletion of
asar
archive files (reference electron/electron#6295, particularly @bpasero's comments as it directly relates to VS Code extensions, for details).I suspect that there is a resource lock happening when reading from or writing to
.asar
files from this extension when it has it "open" in the UI. In this case, I don't really want theasar
files to be read from; I just want to be able to run the build process without having to disable the extension or close Code.I'm also not surprised if this is a Windows-only issue, as I know that they are particular about how FS transactions work, though I also wouldn't be surprised if other platforms have a similar problem.
Until this issue is rectified, however, I will have to disable this extension.
The text was updated successfully, but these errors were encountered: