-
Notifications
You must be signed in to change notification settings - Fork 911
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] Canvas module returning a 404 download #450
Comments
I guess this is because you are running on a Apple ARM CPU? I am not sure if there is a way around this currently if that is the case. I wonder if that linked issue is indeed related, I don't see a fix coming in yet. Any suggestions what I could change as I don't have a machine to reproduce this issue? |
As I correct understand, node-canvas comes from some dependency(ies).
Here are the guides for running ARM64 Linux on QEMU:
or via Docker:
...if that would be helpful |
Perhaps the steps in the bug report can be followed to make sure
If that doesn't work, you could consider removing the deps that require C:\x>npm ls canvas
daedalos@2.0.0 C:\x
├─┬ jest-environment-jsdom@29.7.0
│ ├── canvas@2.11.2
│ └─┬ jsdom@20.0.3
│ └── canvas@2.11.2 deduped
└─┬ pdfjs-dist@4.3.136
└── canvas@2.11.2 deduped |
From pdfjs sources, it like a optional dependency: https://github.com/mozilla/pdfjs-dist/blob/5f07d5a4159bb99eee2f6143d1297f03b45bba58/package.json#L16.
IIRC node-gyp can automatically rebuild a package if libs for your arch/os are not available. I can check later running daedalOS on Debian if you want. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I'm trying to use the Yarn install command within the directory where the project is at. However, the node-canvas module that the project requires is randomly returning a 404 GET request to it's release file on GitHub. The URL it was requesting also returns a 404 message in my web browser. Not sure why this is occurring considering that it was available and working last time I was using DaedalOS on my local machine. Can someone assist me on this?
Log
The text was updated successfully, but these errors were encountered: