@Edgeworth I removed nodejs
on my machine, but I was still able to run logseq
. I'm not familiar with java/javascript at all, so correct me if I'm wrong. I guess the electron's app builder already packages all required runtime dependencies into the app.
Search Criteria
Package Details: logseq-desktop-git 0.9.9.r1.9a8d5ea6a-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/logseq-desktop-git.git (read-only, click to copy) |
---|---|
Package Base: | logseq-desktop-git |
Description: | A privacy-first, open-source platform for knowledge sharing and management. |
Upstream URL: | https://logseq.com |
Keywords: | logseq |
Licenses: | AGPL3 |
Conflicts: | logseq-desktop, logseq-desktop-bin |
Provides: | logseq-desktop |
Submitter: | pychuang |
Maintainer: | bader |
Last Packager: | bader |
Votes: | 4 |
Popularity: | 0.002015 |
First Submitted: | 2021-03-17 09:10 (UTC) |
Last Updated: | 2023-10-05 02:52 (UTC) |
Dependencies (5)
- clojure (clojure-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- nodejs (nodejs-lts-fermiumAUR, nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- yarn (yarn-pnpm-corepackAUR, corepackerAUR, yarn-berryAUR) (make)
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3 4
pychuang commented on 2021-08-19 16:25 (UTC)
Edgeworth commented on 2021-08-19 01:48 (UTC)
This works great for me thank you.
I believe, however, that nodejs (v16) should be in the depends
array.
Note also that if nodejs-lts-erbium (v12) is installed it will fail to build because the fs/promises
module can't be found as it was removed from 12 and added back later in v14+ (see e.g. node #35740 )
pychuang commented on 2021-03-17 09:16 (UTC) (edited on 2022-08-09 16:04 (UTC) by pychuang)
- This package does not support system's
electron
anymore becauseyarn
's electron already supports Wayland. - This package patches the electron version used in package.json so that Wayland backend is supported.
- The desktop file by default launches Logseq with the regular X11 backend. There's an extra action defined in the desktop file to launch with the Wayland backend. How to trigger an action within a desktop file depends on your desktop environment or app launcher.
- If you encounter an error saying
Package subpath './lib/node' is not defined by "exports" in .../logseq/node_modules/postcss/package.json
, try to manually replace yournodejs
withnodejs-lts-gallium
, which provides nodejs 16. The Arch'snodejs
now is at version 17, and some dependencies oflogseq
haven't been coping well with nodejs 17, though they should. - The package uses a user's home directory to store cached npm/clojure dependencies. Hope this speeds up the build process for users who don't have high-speed internet.
Extra notes to people who want to flag this package out-of-date:
This is a GIT AUR package. It has nothing to do with the released versions. Whenever you (re-)build a GIT AUR package, it automatically pulls and (re-)builds with the latest commit and updates the version tag. So as long as the building process works fine, a GIT AUR package is not out-of-date.
Pinned Comments
pychuang commented on 2022-08-09 16:03 (UTC)
electron
anymore becauseyarn
's electron already supports Wayland.Extra notes to people who want to flag this package out-of-date:
This is a GIT AUR package. It has nothing to do with the released versions. Whenever you (re-)build a GIT AUR package, it automatically pulls and (re-)builds with the latest commit and updates the version tag. So as long as the building process works fine, a GIT AUR package is not out-of-date.