vscode-icons not accessible from extension running under WSL
i have my own vscode extension that depends upon the vscode-icons extension.... everything works fine under windows, though i'm having an issue under WSL....
my extension works correctly when installed in WSL; but i've explicitly call out vscode-icons as a dependency, i receive this message when starting-up:
unlike many other extensions, my understanding is that vscode-icons is one that "stays on the local side" when running under WSL.... when i look at the list of installed extension, i see vscode-icons highlighted on the LOCAL side but greyed-out on the WSL side; and of course there is no option to install this extension under WSL....
suggestions anyone????
more information.... if i remove the dependency on vscode-icons from my extension's package.json, i can indeed load remotely....
my problem now is that i can't seem to customize the vscode-icons configuration as when everything is running locally....
in my extension, i dynamically associate icons with certain folders by programmatically changing some bindings in the settings.json file; vscode-icons then exposes a command (which can be invoked remote->local) which effectively refreshes the display....
right now, i don't see any icons being displayed next to the folders of interest....
standing back, i'm looking for an approach to associate icons with a folder/file that has some "semantic" property....
thoughts???
It seems you are dealing with this scenario (https://code.visualstudio.com/api/advanced-topics/remote-extensions#handling-dependencies-with-remote-extensions), and I’m not sure you would be able to change how vscode-icons extension works.
But, I wonder if your extension really needs to be installed on remote. I mean, unless you need full access to the workspace, maybe you could keep your extension as UI (https://code.visualstudio.com/api/advanced-topics/remote-extensions#architecture-and-extension-kinds). Doing so, you would still have access to the vscode-icons API/support.
Hope this helps
- VSCode built-in extension "typescript-language-features" has started a tsserver, is there's a way to interaction with it by my extension?
- VS Code Extension: How do you set an order/priority to the extension's settings/configurations?
- Weird identifier problem in TMLanguage syntax highlighting for AS3
- Visual Studio -- Python Preview Error "Failed to launch the Python Process, please validate the path 'python'"
- Clangd can't find standard library headers and gives weird errors for everything
- How to view inline diff of multiple files at once in VS Code?
- How to prevent Extension Bisect from disabling the extension with the feature I'm troubleshooting
- Error occured while (re-)installing GHC and setting up the VSCode Haskell Plugin
- Can VS Code extensions get URI requests from other programs?
- VS Code extension with webpack and link to node_modules
- Annoying Sound with GitHub Copilot When making in-line suggetions in Visual Studio Code
- Add items to the View container in VSCode extension webview
- Auto run command from vscode extension on file save
- In my VS Code extension, how to add gutter icon with action?
- How do I assign a JSON Schema to a YAML file in my VS Code extension?
- change the color of the cursor in code
- Command not found in VSCode extension
- rust-analyzer failed to discover workspace in vscode
- VS Code Extension - How to add a WebviewPanel to the sidebar?
- Riverpod VSCode quick refactoring options are absent
- F5 not working in Vscode extension development
- How do add esbuild to my vscode extension?
- Why Github Copilot network request not appeared in Visual Studio Code Developer Tools?
- VSCode - Intellisense not working in (.jsx React)
- Is there an event fired on 'IDE is closing' action in API?
- Vscode-specific issue with node-xmlhttprequest-sync: crashes Extension host in Windows; error is caught in MacOS; works as expected in Linux
- Customizing Intellisense style in VSCode
- vs code auto completion
- How to filter out files with certain file extensions in VSCode?
- Unable to uninstall extensions