-
Notifications
You must be signed in to change notification settings - Fork 79
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
Chart JS Nod Canvas Fails To Install #107
Comments
Hi there! As per the NodeJS version section on the docs, |
I see, thank you. Is there a work around for now? And if not, is there an eta for when v18 will be supported? I could downgrade, but I don't want to risk breaking other node packages |
NodeJS
|
Same as @NekitCorp :
https://github.com/Automattic/node-canvas/releases/download/v2.9.3/canvas-v2.9.3-node-v93-darwin-unknown-arm64.tar.gz seems a not so valid path. 404. Anyone know how to fix this? |
So I did some research: node-canvas currently does not support arm
then yarn add chartjs-node-canvas
# or
npm install chartjs-node-canvas And you should be all set! |
PS C:\Users\tortu\Desktop\AI-Moderation-master> npm run start
╭───────────────────────────────────────────────────────────────────╮ my console said this when i started the bot, how can i fix it? |
It seems like Automattic/node-canvas#2025 got resolved and canvas supports Node 18 now. Can the dep be updated? Tried it here real quick: https://github.com/Stannnnn/ChartjsNodeCanvas and it seems to still generate an image. |
@SeanSobey |
@SeanSobey any update? |
Describe the bug
A while ago I ran into an issue where an required dependency canvas was telling me it was complied against a older node version, so I went through the suggested steps of running
npm install
andnpm rebuild
, both of which did not work, so eventually I did a full uninstall of chart js node canvas, then installed it again. But after doing so. this time it was giving me a critical error that it could not make the dependency. What is the reason for this? This is the full error:Versions
The text was updated successfully, but these errors were encountered: