@theia/core
Advanced tools
The @theia/core extension is the main extension for all Theia-based applications, and provides the main framework for all dependent extensions.
The extension provides the base APIs for all Theia-based applications, including:
A Theia extension is a node package declaring theiaExtensions property in package.json:
{
"theiaExtensions": [{
"frontend": "lib/myExtension/browser/myextension-frontend-module",
"backend": "lib/myExtension/node/myextension-backend-module",
}, {
"frontend": "lib/myExtension2/browser/myextension2-browser-module",
"frontendElectron": "lib/myExtension2/electron-browser/myextension2-electron-browser-module",
"backend": "lib/myExtension2/node/myextension2-node-module",
"backendElectron": "lib/myExtension2/electron-main/myextension2-electron-main-module"
}]
}
Each extension can consist of the following modules:
frontend is used in the browser env and as well in the electron if frontendElectron is not providedfrontendElectron is used in the electron envbackend is used in the node env and as well in the electron env if backendElectron is not providedbackendElectron is used in the electron envAn extension module should have a default export of ContainerModule | Promise<ContainerModule> type.
A Theia application is a node package listing Theia extensions as dependencies and managed with Theia CLI.
In order to make application builds more stable @theia/core re-exports some common dependencies for Theia extensions to re-use. This is especially useful when having to re-use the same dependencies as @theia/core does: Since those dependencies will be pulled by Theia, instead of trying to match the same version in your own packages, you can use re-exports to consume it from the framework directly.
Let's take inversify as an example since you will most likely use this package, you can import it by prefixing with @theia/core/shared/:
import { injectable } from '@theia/core/shared/inversify';
@injectable()
export class SomeClass {
// ...
}
@theia/core/electron-shared/...
native-keymap (from native-keymap@^2.2.1)electron (from electron@^30.1.2)electron-store (from electron-store@^8.0.0)fix-path (from fix-path@^3.0.0)@theia/core/shared/...
@phosphor/algorithm (from @phosphor/algorithm@1)@phosphor/commands (from @phosphor/commands@1)@phosphor/coreutils (from @phosphor/coreutils@1)@phosphor/domutils (from @phosphor/domutils@1)@phosphor/dragdrop (from @phosphor/dragdrop@1)@phosphor/messaging (from @phosphor/messaging@1)@phosphor/properties (from @phosphor/properties@1)@phosphor/signaling (from @phosphor/signaling@1)@phosphor/virtualdom (from @phosphor/virtualdom@1)@phosphor/widgets (from @phosphor/widgets@1)@theia/application-package (from @theia/application-package@1.55.0)@theia/application-package/lib/api (from @theia/application-package@1.55.0)@theia/application-package/lib/environment (from @theia/application-package@1.55.0)@theia/request (from @theia/request@1.55.0)@theia/request/lib/proxy (from @theia/request@1.55.0)@theia/request/lib/node-request-service (from @theia/request@1.55.0)fs-extra (from fs-extra@^4.0.2)fuzzy (from fuzzy@^0.1.3)inversify (from inversify@^6.0.1)react-dom (from react-dom@^18.2.0)react-dom/client (from react-dom@^18.2.0)react-virtuoso (from react-virtuoso@^2.17.0)vscode-languageserver-protocol (from vscode-languageserver-protocol@^3.17.2)vscode-uri (from vscode-uri@^2.1.1)@parcel/watcher (from @parcel/watcher@^2.4.1)dompurify (from dompurify@^2.2.9)express (from express@^4.21.0)lodash.debounce (from lodash.debounce@^4.0.8)lodash.throttle (from lodash.throttle@^4.1.1)markdown-it (from markdown-it@^12.3.2)react (from react@^18.2.0)ws (from ws@^8.17.1)yargs (from yargs@^15.3.1)It's possible to change the log level for the entire Theia application by
passing it the --log-level={fatal,error,warn,info,debug,trace} option. For
more fine-grained adjustment, it's also possible to set the log level per
logger (i.e. per topic). The root logger is a special catch-all logger
through which go all messages not sent through a particular logger. To change
the log level of particular loggers, create a config file such as
{
"defaultLevel": "info",
"levels": {
"terminal": "debug",
"task": "error"
}
}
where levels contains the logger-to-log-level mapping. defaultLevel
contains the log level to use for loggers not specified in levels. This file
can then be specified using the --log-config option. Theia will watch that
file for changes, so it's possible to change log levels at runtime by
modifying this file.
It's unfortunately currently not possible to query Theia for the list of existing loggers. However, each log message specifies from which logger it comes from, which can give an idea, without having to read the code:
root INFO [parcel-watcher: 10734] Started watching: /Users/captain.future/git/theia/CONTRIBUTING.md
^^^^ ^^^^ ^^^^^^^^^^^^^^^^^^^^^
Where root is the name of the logger and INFO is the log level. These are optionally followed by the name of a child process and the process ID.
THEIA_HOSTS
theia.app.com,some.other.domain:300080 or 443.FRONTEND_CONNECTION_TIMEOUT
"Theia" is a trademark of the Eclipse Foundation https://www.eclipse.org/theia
1.55.0 - 10/31/2024
FAQs
Theia is a cloud & desktop IDE framework implemented in TypeScript.
The npm package @theia/core receives a total of 6,191 weekly downloads. As such, @theia/core popularity was classified as popular.
We found that @theia/core demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 11 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.