Package Details: fluidd-git r1686.35667236-1

Git Clone URL: (read-only, click to copy)
Package Base: fluidd-git
Description: Klipper web frontend
Upstream URL:
Keywords: 3d klipper printing
Licenses: GPL3
Conflicts: fluidd
Provides: fluidd
Submitter: wlhlm
Maintainer: wlhlm
Last Packager: wlhlm
Votes: 2
Popularity: 0.000000
First Submitted: 2021-02-22 11:15 (UTC)
Last Updated: 2023-10-07 15:58 (UTC)

Latest Comments

wlhlm commented on 2023-09-01 16:03 (UTC)


Thanks for letting me know. Luckily, fluidd has still been compatible with node 16 up until today. Nevertheless, I've bumped it to be prepared once they actually start requiring it.

sl1pkn07 commented on 2023-08-31 14:03 (UTC)

seems needs nore 18.x

xorly commented on 2022-10-31 18:46 (UTC)

Hi, my build is failing on: /home/diggit/.cache/yay/fluidd-git/PKGBUILD: line 31: ./node_modules/.bin/vue-cli-service: No such file or directory

wlhlm commented on 2021-12-13 17:39 (UTC) (edited on 2022-01-01 22:03 (UTC) by wlhlm)

@qubidt Consumers of the AUR are assumed to have base-devel installed (which includes git).

EDIT: I was mistaken on git being part base-devel. Apologies. Pushed updated PKGBUILD.

qubidt commented on 2021-12-09 00:28 (UTC)

makedepends is missing git which causes this error:

ERROR: Cannot find the git package needed to handle git sources.

(might only be obvious when building in a chroot)

wlhlm commented on 2021-08-06 09:08 (UTC) (edited on 2021-08-06 09:12 (UTC) by wlhlm)

@Psych0d0g Yeah, this is a known problem with compiling TypeScript (the language Fluidd is written in). From my research I have gathered that this requires patching some build script, but I still haven't been able to make it work on a Pi 4 with 2GB of RAM. I suspect a Pi 4 with 4GB of RAM will work, but I don't have access to that. My (unsatisfying) solution to this is to build the package on my laptop and copy it over to the Raspberry. This works well since the package has the 'any' architecture.

As an outsider this thing left a sour taste in my mouth from the JS ecosystem. I can compile the Linux kernel no problem, but why do we need to statically allocate 2GB of memory just to "transpile" this dinky webapp? I think we are all doomed.

Psych0d0g commented on 2021-07-11 15:52 (UTC) (edited on 2021-07-11 15:52 (UTC) by Psych0d0g)

Does not build on a raspberry pi3 crashes due to javaScript heap out of memory

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x555d1496d4 node::Abort() [node]
 2: 0x555d0764a8 node::FatalError(char const*, char const*) [node]
 3: 0x555d2ec548 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0x555d2ec718 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0x555d4c0ba0 v8::internal::Heap::EnsureFromSpaceIsCommitted() [node]
 6: 0x555d4c0c8c  [node]
 7: 0x555d4d0e20 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
 8: 0x555d4d1580 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0x555d4d4a34 v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
10: 0x555d4d4aa0 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
11: 0x555d498ac4 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
12: 0x555d800a80 v8::internal::Runtime_AllocateInOldGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
13: 0x555db6f5cc  [node]