-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Joplin: Due to issues with the build due to canvas, we can't build 3.1.24 #142
Comments
Replace |
That's a great idea! I asked upstream to see if they'd put a max version in the package.json esp if they're not actively testing builds with more than one version. 🤷🏾 I'm not a js dev, so maybe that's not standard procedure. To update this, I've extensively testing building (installing deps) canvas and Joplin in docker https://gist.github.com/sahal/ec57d2e63764e7b125fca54267977bdc using the node-slim images from dockerhub. I've put verbose logs in both of the linked Github issues. To summarize:
Again, not sure what's the correct procedure for troubleshooting js dev environments. |
Js is not really my fasion either 😓. But yeah, i think, for the time being, there need to be a version lock on dependencies, atleast for this Arch package. |
joplin-desktop_install_fail_arch_13dec2024.txt Just sharing that this issue still exists, and I didn't see anything in the AUR that instructs of an actual workaround (or fix?) from the maintainer. I've attached the entire log of my install that demonstrates the errors seen, would really appreciate if this can be permanently addressed, thanks! |
This is an issue with Joplin, for which the developers have not responded (see linked issue). Its related to building the The official package does build because the developers use an older version of node.
|
Still haven't heard back from Joplin. The github bot marked the issue as stale. I did fork the repo and run their own github action that shows the failure though. This is not unique to arch. |
canvas@2.11.2
with Node.js v22.11.0 Automattic/node-canvas#2448 andCreated this to maybe find a work around.
The text was updated successfully, but these errors were encountered: