Theia: Folder Plugin not Working in Theia Build Local with Plugins of VS Code

Created on 8 Sep 2019  路  10Comments  路  Source: eclipse-theia/theia

Description

I have been using theia doing my own build.
and following this tutorial to use vs code plugin

https://github.com/theia-ide/theia/wiki/Testing-VS-Code-extensions

It doesn't work when I add the plugins in the folder.

only work when I use this command when theia is running

"1Alternatively, you can use the command "Deploy plugin by id" from the command palette. When asked for a parameter, enter the following: vscode:extension/. "" stands for the "Unique Identifier" from the extension homepage in the VS Code Marketplace."

but when leaving theia and restarting the plugins are not loaded and I have to do the same process again

Reproduction Steps

  • 1 - download any extension
  • 2 - create folder plugins and add your extension
  • 3- start theia and click in view > plugins with message :

plguin

  • 4 - in Deploy plugin by id > vscode:extension/ works

  • 5 - close Theia and start again , is not loader plugin .

he not saved the plugins

OS and Theia version:
all

Diagnostics:
N/A

question

All 10 comments

For additional information, what VSCode extension did you use when testing?
Can you include the logs when running the application?

here the folder with extensions that use .

pluginList

and with Theia in start

theia

now , if add any extension for example : vscode:extension/redhat.java

new

if I stop Theia, the plugin is not loaded

I have to do the process again to add the plugin

@Daniel-Dos
I tested it out myself and it works correctly:
I followed the following steps:

  1. build Theia from sources
  2. create a plugin directory at the root of the project
  3. download a VSCode extension (.vsix file) - in my case the gitignore extension
  4. start the application:
$ (cd examples/browser/ && yarn start)
yarn run v1.12.3
$ theia start --plugins=local-dir:../../plugins
root INFO Theia app listening on http://localhost:3000.
root INFO unzipping the plugin ProxyPluginDeployerEntry {
  deployer:
   PluginVsCodeFileHandler {
     unpackedFolder:
      '/private/var/folders/h2/m_txl3zj69x8nnhqmj03r2000000gn/T/vscode-unpacked' },
  delegate:
   PluginDeployerEntryImpl {
     originId: 'local-dir:../../plugins',
     pluginId: 'codezombiech.gitignore-0.6.0.vsix',
     map: Map {},
     changes: [],
     acceptedTypes: [],
     currentPath:
      '/Users/vincentfugnitto/workspace/theia/plugins/codezombiech.gitignore-0.6.0.vsix',
     initPath:
      '/Users/vincentfugnitto/workspace/theia/plugins/codezombiech.gitignore-0.6.0.vsix',
     resolved: true,
     resolvedByName: 'LocalDirectoryPluginDeployerResolver' },
  deployerName: 'PluginVsCodeFileHandler' }
root INFO PluginTheiaDirectoryHandler: accepting plugin with path /private/var/folders/h2/m_txl3zj69x8nnhqmj03r2000000gn/T/vscode-unpacked/codezombiech.gitignore-0.6.0.vsix
root INFO Resolved "codezombiech.gitignore-0.6.0.vsix" to a VS Code extension "[email protected]" with engines: { vscode: '^1.18.0' }

I see that the extension is loaded:

Screen Shot 2019-09-08 at 7 13 40 PM

here the folder with extensions that use .

pluginList

Where do you place your plugins?
From the logs I can see that they are not being loaded.

I put the plugins in a plugin folder along with theia build files

folder

I put the plugins in a plugin folder along with theia build files

folder

I assume you're running on docker, and that you've built your own ide?
You haven't built the application from sources (the main repository) as described in the first step of the guide?

'm not climbing the docker,

I built the IDE itself as per this documentation

https://www.theia-ide.org/docs/composing_applications

"Build your own IDE"

'm not climbing the docker,

I built the IDE itself as per this documentation

https://www.theia-ide.org/docs/composing_applications

"Build your own IDE"

I see, the guide you initially mentioned is mainly for testing purposes. The first step in the guide describes building the application from sources. This means cloning the theia repository and building it, not composing an application.

hi @vince-fugnitto ,

now work .
thanks .

hi @vince-fugnitto ,

now work .
thanks .

Great! I'm glad :)

Was this page helpful?
0 / 5 - 0 ratings