ObsidianRuntimeVersions
The concrete JS runtime versions an installer’s Electron shell ships — the entire process.versions object, read empirically by booting that installer over CDP (see scripts/collect-runtime-versions.ts). Absent for versions not yet collected (or that could not be booted).
These are the WINDOWS (.exe) values, and that matters. A given Electron version does bundle the same Node / V8 / Chromium everywhere — but the Electron version itself is a property of the installer, not of the release, and two installers of the same Obsidian version can differ: 1.12.4 shipped Electron 39.6.0 in its .exe and 39.7.0 in every other installer, and 1.8.10 shipped 34.2.0 vs 34.5.2. This field carries one flat value, measured on the .exe — the installer that, with the .dmg, is published for all 106 installer-bearing releases. So a consumer pinning a macOS or Linux installer should treat electron as accurate to the patch only for the 104 releases where the platforms agree. The collection workflow boots all three platforms and reports any new divergence.
The index signature carries every key process.versions exposes for that Electron build — beyond the four well-known ones below, that typically includes ares, brotli, cldr, icu, llhttp, modules, napi, nghttp2, openssl, tz, unicode, uv, zlib (and, on newer Electron, ada, simdjson, …). The exact set varies by Electron version, which is why it is captured wholesale rather than as a fixed field list.
Import:
import type { ObsidianRuntimeVersions } from 'obsidian-integration-testing';Signature:
export interface ObsidianRuntimeVersionsProperties
| Property | Type | Description |
|---|---|---|
| chrome | string | The bundled Chromium version, e.g. '114.0.5735.289'. |
| electron | string | The bundled Electron version, e.g. '25.8.1'. |
| node | string | The bundled Node.js version, e.g. '18.15.0'. |
| v8 | string | The bundled V8 version, e.g. '11.4.183.23'. |
Links to this page: