Logseq

Issues

Warning: Electron 27 is outdated and insecure. Output will tell you to explicitly allow insecure packages.

Overriding the Electron version

Note: The text of your notice

As an alternative to allowing Electron 27 as an insecure package, one could override the version of Electron used in the package itself. There are two general choices one could go for:

• Electron 31: this is the pinned version of Electron in Logseq's lock file. However, this version is still EOL;
• Electron 34: the latest version of Electron.

The approach of bumping to Electron 34 has been superficially tested; the app seems to run and documents are being saved, however there is no guarantee nor in-depth testing for it. If this is still not enough to hinder your curiosity, this is how one could achieve it in configuration.nix:

/etc/nixos/configuration.nix

let
  # Create a customized version of logseq
  logseq-patch = pkgs.logseq.override {
    electron_27 = pkgs.electron_34;
  };
in
{
  ...
  users.users.[user].packages = with pkgs; [
    ...
    logseq-patch
  ];
}

You can check the talk page for possible avenues further.