Is the argument --builtin-extensions-dir fully supported?

[avsthiago]

Hi,

I'm trying to set up two locations to store extensions, built-in and user specific ones.

I'm using the following command to start code-server.

code-server --extensions-dir /home/user/.extensions --builtin-extensions-dir /opt/code-server/extensions 

I can see and use the extensions inside the --extensions-dir, the problem is with the built in ones. They all appear as disabled and I couldn't find a way to enable them.

This is a comparison of what I see when I use the arg --builtin-extensions-dir with code-server and VS Code locally. VS Code has a button to enable the extension.

Does anybody know if I'm missing something or if the arg --builtin-extensions-dir is still under development?

[jsjoeio]

Interesting. I see --builtin-extensions-dir used in our tests but it's not printed when you use --help. It may not be passed through correctly. @code-asher any ideas?

[code-asher]

Hmm it looks to me like we are passing it through. We will have to poke into it more.

[avsthiago]

FYI, the solution/workaround for me was to install the extensions inside the default built-in extensions folder /usr/lib/code-server/lib/vscode/extensions/. I used the following command.

code-server \ 
--install-extension [email protected] \
--install-extension [email protected] \
--extensions-dir /usr/lib/code-server/lib/vscode/extensions/