Ignoring option install-extension: not supported for code-insiders #27138
-
I am trying to run this file: dotfiles/plugins.sh at ae5e8d992e9479793d86c232ea82deb66b1e3f2a · sobolevn/dotfiles · GitHub It contains several Error:
What are the possible solutions here? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Hi @sobolevn, installing extensions as part of dotfiles poses some challenges, since dotfiles install runs in parallel with user connection, and there’s no guarantee you are connected by the time it runs, or even which VS Code version you are connecting from (insiders, stable, etc). Without knowing which VS Code version you are connecting from, you cannot know which version to install the extension into. There are two alternative recommended methods for installing extensions automatically:
I would use (1) for extensions that are mostly personal preference like themes and other UI-related extensions, and (2) for things like language extensions, SDKs, debuggers, etc which are needed to build and run the project, and which everyone in that repo is going to need. Hope that helps! |
Beta Was this translation helpful? Give feedback.
-
Thanks for your help! Settings sync kinda works, but some minor things are not clear:
|
Beta Was this translation helpful? Give feedback.
-
For (1), you shouldn’t need to do anything to enable settings sync. It’s on automatically in Codespaces. Let us know if you are seeing something different. For (2), I don’t think that’s supported currently. There’s not a great way to have Codespaces-specific config that is applied to all codespaces and not roamed back to desktop. cc @sandy081 who works on settings sync for VS Code. |
Beta Was this translation helpful? Give feedback.
-
Might be a good idea to add some hooks like |
Beta Was this translation helpful? Give feedback.
Hi @sobolevn, installing extensions as part of dotfiles poses some challenges, since dotfiles install runs in parallel with user connection, and there’s no guarantee you are connected by the time it runs, or even which VS Code version you are connecting from (insiders, stable, etc). Without knowing which VS Code version you are connecting from, you cannot know which version to install the extension into.
There are two alternative recommended methods for installing extensions automatically: