-
Notifications
You must be signed in to change notification settings - Fork 14
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
Some extensions b*tch about not being able to write into the extensions directory #46
Comments
Yeah. The same is happening with this extension: https://open-vsx.org/extension/golf1052/base16-generator, I have used it to auto select various themes using base16 colors, but It is throwing errors, only If I install it this way. Otherwise if I install from extensions tab inside vscode, it works. |
Same for the catppuccin theme. |
I recently came across this Reddit post. The post and comments mention Nix-Bwrapper and NixPak for sandboxing packages. Maybe we can wrap extensions that want to write to the extensions directory, and bind another writable directory in their write location. |
@AmeerTaweel, have you tried to implement your solution? If yes, what were the outcomes? |
Sorry for the late reply @deemp. I tried using both Nix-Bwrapper and NixPak to sandbox VSCode extensions, but I was unsuccessful. I could not reproduce @yangm97's issue with I was able to reproduce @mobsenpai's issue with However, I still believe this approach might work with VSCode extensions that contain binaries. |
Noticed this at the console:
I suppose this extension in particular isn't following the best practices and stuff, but I wonder what would be a fix that doesn't depend on upstream.
The text was updated successfully, but these errors were encountered: