Immich provides release files, I wonder if there is a prebuilt frontend there? Just to avoid building that mess:
--- Last few GCs --->
[25393:0x598a99c4c000] 49922 ms: Scavenge (interleaved) 472.4 (479.9) -> 471.1 (484.4) MB, pooled: 0 MB, 16.16 / 0.00 ms (average mu = 0.208, current mu = 0.111) allocation failure;
[25393:0x598a99c4c000] 50428 ms: Mark-Compact (reduce) 475.3 (484.4) -> 473.1 (479.6) MB, pooled: 0 MB, 110.03 / 0.00 ms (+ 322.6 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 506 ms) (average mu = 0.244, c
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0x598a815eb9db node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
2: 0x598a81ab9f64 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
3: 0x598a81aba339 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
4: 0x598a81d0557c [node]
5: 0x598a81d055a4 [node]
6: 0x598a81d1c8fe [node]
7: 0x598a81d1fb04 [node]
8: 0x598a82772a67 [node]
/home/dmig/.cache/yay/immich/PKGBUILD: line 70: 25382 Aborted (core dumped) npm run build
==> ERROR: A failure occurred in build().
Aborting...
Pinned Comments
aliu commented on 2026-01-17 21:44 (UTC) (edited on 2026-01-17 21:46 (UTC) by aliu)
Upstream recommends using docker, for which they have pre-built images (that might also work with podman).
aliu commented on 2025-10-25 02:49 (UTC)
PostgreSQL 18 is coming to the Arch repos. Before upgrading, backup the files for vectorchord and pgvector somewhere, and then follow https://wiki.archlinux.org/title/PostgreSQL#Upgrading_PostgreSQL instructions. (In the next release, I'll also update the postinstall message to recommend changing postgresql.conf instead of doing ALTER SYSTEM SET.)
Also, you may find yourself updating VectorChord in this process. When doing so, remember to follow the migration steps at https://docs.immich.app/administration/postgres-standalone/#updating-vectorchord .
aliu commented on 2025-08-21 15:21 (UTC)
immich-web (localhost/immich-server:2283) used to be broken for some users of this package.
As @yparitcher also noticed, this was most likely caused by the following additions to .gitignore from f4e0aad2c495, which have since be reverted:
The reason—for both this change sometimes and unpredictably breaking the build, and builds under a clean chroot still working—is unknown. I meant to investigate this on 2025-08-19 while updating the package but called it a day due to the unpredictability and long time of building. Help with figuring out why this happened would be greatly appreciated.
aliu commented on 2025-06-30 02:49 (UTC) (edited on 2025-07-01 16:35 (UTC) by aliu)
You may notice pacman refuse to upgrade this package, saying warning: cannot resolve "vectorchord", a dependency of "immich-server".
This is due to required manual intervention within the immich server database.
Newer versions of immich server have deprecated pgvecto.rs in favor of vectorchord.
Before updating from
1.133.1or older, please follow steps 1 and 2 of the manual migration steps (should be the second dropdown) at https://immich.app/docs/administration/postgres-standalone/#migrating-to-vectorchord and uninstall pgvecto.rs.Remember to remove references to "vectors.so" (which is shipped by pgvecto.rs) in shared_preload_libraries before pgvecto.rs in uninstalled. (For vectorchord to work, you'll need to add "vchord.so" to shared_preload_libraries after the upgrade as well.)
After that, you may upgrade this package. Please remember to follow steps 4 and 5 of the manual migration steps after the upgrade is finished to prevent data loss.