npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@devpodio/core

v0.6.3

Published

Theia is a cloud & desktop IDE framework implemented in TypeScript.

Downloads

50

Readme

Theia - Core extension

See here for a detailed documentation.

Theia Extension

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 provided
  • frontendElectron is used in the electron env
  • backend is used in the node env and as well in the electron env if backendElectron is not provided
  • backendElectron is used in the electron env

An extension module should have a default export of ContainerModule | Promise<ContainerModule> type.

Theia Application

A Theia application is a node package listing Theia extensions as dependencies and managed with Theia CLI.

Logging configuration

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 [nsfw-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.

License