Over the last month, the Eclipse Che community has been adopting Eclipse Theia as the default web IDE provided with Che developer workspaces. We’ve enriched the Eclipse Theia with a plug-in model to provide VS Code extension compatibility. This blog post explain why we decided to add the plug-in model to Eclipse Theia and what are the benefits when it’s used with Eclipse Che developer workspaces .
In Eclipse Che 6, it is possible to develop and plug-ins on top of the GWT IDE but it is not possible to load them at runtime without stopping/recompiling and then reloading the IDE.
A lot of people wanted to improve that extensibility model. For the upcoming version of Eclipse Che, Che 7, we ended up with the following requirements:
- Plug-ins should be loaded at runtime easily and it should not involve any compilation step at that time. Plug-in should be already compiled and IDE should only load the code.
2. A plug-in shouldn’t break the whole IDE if it is not well written. For example if I load a broken plug-in, I should still be able to use the current IDE
3. In Eclipse Che, we wanted to guarantee that any plug-in shouldn’t block the main functions of the IDE like opening a file or typing. It could allow to identify if it’s the main product that has issue or if it’s due to a specific plug-in. Also, if two plug-ins are relying on the same dependency but in different versions it shouldn’t be a problem as well, each plug-in using its own dependency.
The API provided is a low-level API. It’s a great API but as you can change everything you can also break everything. And it is difficult to know each entry point.
Eclipse Theia has been considered to be the alternative IDE in Eclipse Che. This IDE can be embedded and used in Eclipse Che as it’s a web based IDE and use modern technologies like React and is written in TypeScript. This IDE had only a single extension model: Theia extension.
The problem is that this extension model was mainly designed to develop customs IDE so it has issues for our requirements:
With Eclipse Theia extensions, once a new Theia extension is
added, the whole IDE is recompiled. If an extension is not so
clean, you may broke the full IDE. It’s a problem when you want to
allow users to add custom plug-ins.
Let’s imagine you open a Che workspace and you see a blank page due to a compilation failure instead of the IDE…
Extensions are retrieved from npmjs repository. It’s nice but npmjs has tons of libraries and when you install an extension, it will download all dependencies again and again. If you’ve many dependencies, it may break. You might want to use a local repository easily as well.
Theia extensions allow to customize the whole IDE but as for the GWT IDE in Eclipse Che 6, extensions may easily break the full IDE.
It’s very nice when you are advanced users or power users but when you want to write your first extension, you’ve to master inversify and dependency injection and also you need to know which class is doing what and which interface you need to implement.
So this extension model was not matching the requirements. At Red Hat, we decided to bring another extensibility model into Eclipse Theia: the Theia plug-ins
This new extensibility model has been integrated into Eclipse Theia upstream.
Here are key aspects of Theia plug-ins:
Plug-ins can be loaded at any time at the runtime without having to restart/refresh the IDE.
Eclipse Theia plug-ins are packaged into
files and contain all the runtime code for the plug-ins. No need
to download anything else when you load this plug-in at runtime.
You might want to bring a dependency injection framework into your
plug-in but it’s up to you. The model is as simple as importing
only once namespace
(through npmjs package
@theia/plugin) and you can get all stuff from this entry point with code
completion on this object. Then you implement the lifecycle of
your plug-in by implementing
Sample code of a theia plug-in
It is a protocol. It means that we can run plug-ins anywhere. Some plug-ins can run in worker threads of the browser (they are called frontend plug-ins) or it can run on server side on separate processes (backend plug-ins). It’s easy to handle other kind of namespace, including VS Code extensions.
It’s backward compliant. As plug-in model is provided through a TypeScript declaration file, even if the implementation of this model is entirely rewritten or if code refactoring is done on many Eclipse Theia classes, the model stay unchanged.
As it’s a high level API, you may not be able to break the whole IDE but you may not do what you want in the way you want but surely there are many possibilities.
Eclipse Che is using containers for the tooling. Theia plug-ins
sometimes, plug-ins writers need some dependencies that are not
dependencies. For example if people write a Language Server for
Java, this plug-in will probably require java. So it might implies
that the container that runs Eclipse Theia should have java
already installed on it.
This is why in Eclipse Che, it’s possible to run each Eclipse Theia plug-in in its own container, allowing to use any system dependency from this plug-in.
By default all plug-ins are executed as separate processes in the Theia container.
VS Code Extensions
Eclipse Theia Plug-in protocol being extensible, support of VS Code API is being added inside Eclipse Theia. It allows to have some VS Code extensions running inside Eclipse Theia.
For example it’s possible to use SonarLint VS Code extension from VS Code marketplace
Try Eclipse Che 7 Now!
Want to give a try to the new version of Eclipse Che 7? Try the following:
Click on the following factory URL : https://che.openshift.io/f?id=factoryvbwekkducozn3jsn
Or Create your account on che.openshift.io, create a new workspace and select “Che 7” stack.
You can also test that locally, by installing the latest version of Eclipse Che: Quick Start with Eclipse Che.
Want to learn more?
Blog post about Eclipse Che 7:
- Read the blog post serie about Eclipse Che 7.
Join the community: