electron 40+ plugin loading not working

[TomaSajt]

The Electron version has already been bumped from 39 to 41, but the plugin loading issues that got introduced in Electron 40 are not yet fixed.
Probably the same fixes are needed as in the main repo logseq/logseq#12741.

I am not nearly knowledgeable about the codebase to do this myself, sorry.

It would be great to have this, as currently, the users of this package in nixpkgs get a hard-to-ignore warning that the package is using Electron 39 which is EOL.

[luxebenen]

This would be very welcome, I cannot get any plugins to load with the latest version.

[Coda-Coda]

I'd also really appreciate this being fixed please. Especially since the DB version still doesn't yet support two-way sync between DB and markdown (see: logseq/logseq#12593). So there's still a range of use-cases which rely on directly being able to edit markdown that the DB version doesn't support (yet). And having the OG version working properly for those who prefer not to switch to the DB version would also be really great to have in the long term too.

[3rdPix]

I am also interested in this fix; I currently cannot access Logseq because of this issue with electron being EOL. However, as well as OP, not nearly qualified to solve it. Putting it out there so that becomes known there are more souls interested in this

[arrowd]

Can we please have a proper Logseq OG release supporting the newer Electron? In its current state the OG version is abandonware.

[CR0CKER]

Opened #50 against version/file for this.

The cause is not the Electron version itself. Electron 40 tightened opaque-origin rules:
loading the renderer from file:// makes the parent origin opaque, which breaks the
postMessage handshake plugin iframes depend on — so on 40+ no plugin loads, on any Electron
after that point. Upstream fixed the same thing for the DB version in logseq/logseq#12741 by
serving the renderer over the privileged lsp:// scheme instead. That port is most of the work
here, adapted for this tree (constants live in libs/src/helpers.ts rather than common.ts, the
production entry is electron.html, and the dot-root is ~/.logseq-og).

Two things follow from it that the upstream patch does not cover, and that you hit immediately if
you only take logseq/logseq#12741:

• Themes break. Plugin themes register their stylesheet URLs in the bare legacy form
  lsp://logseq.io/<pid>/…, and those URLs are persisted in preferences.json and
  localStorage — so they survive the upgrade and then fail to resolve. The symptom is a theme
  that appears in document.styleSheets while none of its colours apply.
• Plugin HTTP breaks. An lsp:// frame has a real origin, so Chromium starts enforcing CORS
  on requests plugins make; file:// never did. Readwise sync, url-title-tagger, and
  Zotero/Syncthing-backed plugins all stop working (Bug (?) / Help With CORS Checks For Plugins logseq#12736). Restoring this grants
  plugins nothing new — logseq.Request already reaches any host through the main process with
  no CORS at all — it just stops penalising plugins that use plain fetch.

While upgrading, better-sqlite3 12.10.0 no longer compiles against Electron 43's V8; 13.0.3
fixes that and ships N-API prebuilds, which takes it off the per-Electron-major rebuild treadmill
entirely.

Where it has actually been run: a packaged Electron 43.4.1 build on Linux (aarch64,
Asahi/Fedora). 15 dot-root plugins loading and executing across both the logseq.com/plugins/ and
logseq.io/plugins/ routes; themes verified with an A/B of computed styles against 0.10.15 over
CDP; Readwise sync (i.e. plugin HTTP) working again; both external plugins loading over the new
/external/ route, one with an HTML entry and one with a .js entry, freshly installed through
Load unpacked plugin and again after a restart; and better-sqlite3 13 smoke-tested under
Electron 43 for FTS5, triggers and MATCH. macOS and Windows packaging are not tested by me —
I don't have the hardware — so that is the gap someone else would need to cover before a release.

One upgrade note worth flagging early, because it looks like data loss and isn't: the
renderer origin moves from file:// to lsp://logseq.com, and localStorage is keyed by origin,
so UI preferences silently reset to defaults on first launch. The visible one is radix-color
returning to logseq, which activates the built-in Solarized-teal background and overrides theme
plugins. Sidebar widths reset the same way. This belongs in the release notes whenever a build
ships.

@arrowd — on the nixpkgs side, note that from Electron 42 the npm package no longer downloads its
binary in a postinstall hook; it fetches on first use instead. An offline or sandboxed build
needs the cache primed explicitly, or yarn install finishing in a few seconds looks like a
failure when it isn't.

Happy to split the work differently if a maintainer prefers — the Electron bump and the plugin
fix can be reviewed separately, though neither is much use without the other.

[arrowd]

JFYI, Logseq OG port was removed from FreeBSD Ports today due to expired Electron.