[electron] Incomplete process.versions can cause native loading issues at the backend

[kittaakos]

Description

Inside a bundled electron application, we lose the electron and chrome properties from the process.versions. This can cause module-loading issues inside a bundled Theia application. For instance, one cannot require grpc at the Theia backend.

Originally from here:

The electron-v4.2-darwin-x64-unknown file is the correct one for Electron 4.2

This helped a lot 👍 In our app we fork several processes from the electron main. So I logged process.versions in the main electron module and at the very first grpc require and I can see a difference.

{
  "http_parser": "2.8.0",
  "node": "10.11.0",
  "v8": "6.9.427.31-electron.0",
  "uv": "1.23.0",
  "zlib": "1.2.11",
  "ares": "1.14.0",
  "modules": "69",
  "nghttp2": "1.33.0",
  "napi": "3",
  "openssl": "1.1.0",
  "electron": "4.2.12",
  "chrome": "69.0.3497.128",
  "icu": "62.2",
  "unicode": "11.0",
  "cldr": "33.1",
  "tz": "2019a"
}

{
  "http_parser": "2.8.0",
  "node": "10.11.0",
  "v8": "6.9.427.31-electron.0",
  "uv": "1.23.0",
  "zlib": "1.2.11",
  "ares": "1.14.0",
  "modules": "69",
  "nghttp2": "1.33.0",
  "napi": "3",
  "openssl": "1.1.0",
  "icu": "62.2",
  "unicode": "11.0",
  "cldr": "33.1",
  "tz": "2019a"
}

11a12,13
>   "electron": "4.2.12",
>   "chrome": "69.0.3497.128",

If apply the following hack inside my bundled app, something like this, then it works:

process.versions.electron = "4.2.12";
process.versions.chrome = "69.0.3497.128";
"use strict";

// ...

var grpc = require("grpc");

Reproduction Steps

OS and Theia version:

Diagnostics: