Arch Linux User Repository

Thank you dosenpils and masterkorp for supporting the package.

I replaced the PKGBUILD with the version I wrote for the archlinuxcn repo. I will do my best to follow the latest nodejs and electron versions.

Please try to build in a clean chroot (i.e., with extra-x86_64-build from devtools package) if you have problems building the package.

If you want to use the fcitx input method under wayland, please complete the following configuration:

cat .config/electron25-flags.conf 
--enable-wayland-ime
--ozone-platform=wayland

I tried to install the joplin-desktop package and it is complaining that I am missing the dependency "nodejs<23".

From terminal:

==> Validating source files with sha256sums... joplin-desktop.sh ... Passed joplin-desktop.desktop ... Passed joplin-3.3.13.tar.gz ... Passed ==> Making package: joplin 3.3.13-1 (Wed 09 Jul 2025 02:44:41 PM) ==> Checking runtime dependencies... ==> Missing dependencies: -> nodejs<23 ==> Checking buildtime dependencies... ==> ERROR: Could not resolve all dependencies. error: failed to build 'joplin-3.3.13-1 (joplin-desktop)': error: packages failed to build: joplin-3.3.13-1 (joplin-desktop)

My node version installed:

❯ node --version v24.3.0

Hi, author of the mentioned nixpkgs PR here. I got joplin-plugin-backup to work by packaging the whole dist/linux-unpacked dir instead of just resources, and launching the generated joplin executable. Actually, everything outside of resources is files from electron itself, and it works as well if you copy those directly from electron and the resources dir from the build. Symlinking them doesn't work unfortunately. I don't know why it breaks otherwise, maybe someone has a better idea for working around this.

@gerum100 Thank you for reporting. It's probably similar problem as joplin backup plugin (https://github.com/JackGruber/joplin-plugin-backup/issues/92). And since it also appears in aur/joplin-beta and even nix's native package (https://github.com/NixOS/nixpkgs/pull/417048), packaging asar is probably the issue. But this package is supposed to be as native as possible so I'm not intended to switch. Before the community figures out the solution, you can try joplin-appimage package or simply use the upstream appimage.

The packaging approach to only package the asar is somehow broken.

I do not exactly know what the problem is (I am not a js/electron developer) but there seems to be at least one issue: If you install the yesyoukan plugin, then "Tools / Create Kanban board", and open the resulting note, there should be an eye icon on the top right corner to activate the plugin, but it does not show up.

The AppImage that is also created during the build ("${srcdir}/joplin-${pkgver}/packages/app-desktop/dist/Joplin-3.3.13.AppImage" ) does not have that problem so it is a problem with the bundling, not the app or plugin itself.

After the update to 3.3.13-1 it still shows on pamac's update list as 3.2.13-2. No amount of updates changes that.

"nodejs<23" "nodejs>20" may bad for some tools to automate everything compared with writing nodejs-lts-* directly.

@sphere101 Please see the previous discussion. This is intentional. nodejs 23 won't compile the package and Arch provides LTS versions for nodejs. If you don't want to switch the system nodejs, you can build the package in a chroot (see pinned message). I am not 100% sure but I think after the package is built it will work with latest nodejs.

@AmbassadorDave Thank you. I added libvips as a dependency for the split package joplin-desktop.

I believe the build dependencies need to updated to support the latest version of nodejs...

==> Checking runtime dependencies... ==> Missing dependencies: -> nodejs<23 ==> Checking buildtime dependencies...

It's checking for a version below 23, however the latest version is 23..

akrahn@figaro ~]$ node --version v23.11.1

Can someone update pls...

@flexusjan I had the same issue and installing libvips worked for me as well, thanks! @cuihao Perhaps libvips ought to be added as a Dependency now? Much appreciated you've taken on this package!

Sorry. This is no longer bundling it. Misunderstanding by another reason.