search for extensions via command line

[typekpb]

• VSCode Version: 1.2.1-1465908640
• OS Version: RHEL 7.2

I've noticed there is a way to manage extensions via cli: https://code.visualstudio.com/docs/editor/extension-gallery#_command-line-extension-management

One step I miss in the cli is however to search for extensions.
I'd love to have some command for that, possibly something like:

code --search-extensions <string>

where <string> could be substring in the extension name - as shown in the UI, or the explicit one, as used for installing via cli

[ergunsh]

Hey! I can pick this 😇

[pradeepmurugesan]

@joaomoreno I would like to give it a try.. But how can I execute the cli from the local build.

I compiled and tried out the following command

node out/cli.js --lsit-extensions

but I got an error

Detail:  { Error: Cannot find module 'original-fs'
    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at NodeScriptLoader.load (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:732:39)
    at OnlyOnceScriptLoader.load (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:578:32)
    at loadNextPath (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:1426:41)
    at Object.errorback (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:1434:25)
    at OnlyOnceScriptLoader.triggerErrorback (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:591:36)
    at /Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:578:151 code: 'MODULE_NOT_FOUND' }
Error: Cannot find module 'original-fs'
    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at NodeScriptLoader.load (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:732:39)
    at OnlyOnceScriptLoader.load (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:578:32)
    at loadNextPath (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:1426:41)
    at Object.errorback (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:1434:25)
    at OnlyOnceScriptLoader.triggerErrorback (/Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:591:36)
    at /Users/pmurugesan/personal/microsoft/fork/vscode/out/vs/loader.js:578:151

I guess this may be is the lack of electron while executing the local cli. But not sure what will fix this.

kindly help me here..

[joaomoreno]

Use ./scripts/code.cli.sh instead.

[BuraChuhadar]

@joaomoreno #61175 should add this feature.

[sandy081]

@BuraChuhadar I suppose the request here is to search for extension from Marketplace and not only installed extensions.

@typekpb Can you please confirm? Also may i know what is the use case for the request?

[BuraChuhadar]

@sandy081 I am OK if we need to add search for extensions from Marketplace. I can add more details in this implementation if you would like where it would say;

1- If an extension is installed, it would show as "installed" next to it
2- If an extension is from marketplace it can show as "not installed"
3- If the user is offline then it would say "Couldn't connect to the marketplace."

The code then would differentiate between installed and non-installed extensions and filter out from the Marketplace search. Obviously this is opening a can of worms because once you have search from marketplace then you would also want to install extensions from marketplace as well. Let me know your thoughts.

[sandy081]

Before going to implementation I would like to know the use case for this requirement.

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!