Coverage
This page answers one question before you start building: is the thing I need already there?
Expand a category to see every module or standard with its status.
- Full means the part a normal app touches works.
- Partial means the core works and the specific corners that do not are named in the entry.
- Stub means it resolves so a dependency check passes, but does nothing.
- Planned means it is in scope and not built yet.
- Out of scope means it makes no sense in a desktop GTK app and will not be built.
The pillar totals are regenerated from the project’s own status data on every site build, so they cannot drift from it. The three inventories under them are curated by hand, and we run more real-world packages end to end than the selection shown here, so read a missing entry as “not listed”, never as “not supported”.
What the numbers measure is the APIs gjsify implements itself, on top of GNOME libraries. There are most of them on GJS, which has no node:fs, no fetch and no <canvas> of its own. Node, Bun and Deno have all three, so a --app node build takes them straight from the runtime and most of the Node and Web entries below never enter that bundle. A few entries are gjsify’s own code on every runtime, because no JavaScript runtime ships them at all, DOMParser, <canvas> and WebGL among them. The Adwaita, framework and tooling entries are runtime-independent to begin with.
For what is validated on Node.js, Bun, Deno and in the browser, see Runtimes; for which operating systems each native bridge reaches, see Platform Support.
Project Coverage
190 of 193 pillar entries implemented
Every category of the project status snapshot, rendered as a live progress bar. The data file is regenerated from the status data and the package manifests on every build, so the bars never lag behind reality.
Node.js API Coverage
38 of 41 Node.js modules
User-facing Node modules backed by GLib, Gio, Soup, and native Vala bridges. 3 deprecated or browser-irrelevant modules ship as stubs so dependency checks resolve.
Web Platform Coverage
34 of 59 web standards
Coverage of relevant W3C and WHATWG standards, including 10 APIs that are explicitly out of scope for desktop GTK apps (Service Worker, FS Access, Web Bluetooth, …).
Integration Tests
22 npm packages, end-to-end
Real-world libraries whose own test suites (or a curated subset) run unmodified against @gjsify/*. Catches regressions that polyfill-internal tests would miss.
Parsing
Build tooling
Filesystem
Language core
Process & CLI
Networking
Streams & workers
Peer-to-peer
If something you need is missing
Section titled “If something you need is missing”- A partial module is often good enough. Its entry names exactly what is not there.
- If a global is the problem rather than a module, one build flag usually fixes it. How It Works walks through it.
- Otherwise, open an issue on GitHub and say which package you are trying to run. That is the signal that moves things up the list.