-
Notifications
You must be signed in to change notification settings - Fork 50
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
Node 20 Compile Issues #169
Comments
As far as I know the latest version of |
true |
Apologies, I ran into this issue, but it's not clear what you mean by update non to 2.17? Where would I do this? |
actually in package.json we add an override node-gyp version :
but since then we move forward to @picturae/mmmagic to fix an other issue too. |
so I was able to install @picturae/mmmagic without issue.. the weird thing is that it looks like exactly the same code base as the default mmmagic in this repo. |
In @picturae/mmmagic |
Thanks @jonmaim! We adoped the following changes via pnpm patch: package.json
binding.gyp
those changes came from this commit: 35978fb#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519 We plan to stay with @mscdex / mmmagic, so it would be nice to have those changes merged, when verified no other conflicts occur. Edit: It already has an pr: #171 |
I've just updated the @picturae/mmmagic package to support node 22 as well. It's now all in the master branch, but I've left the node-20 branch for now. An updated scoped version (@picturae/mmmagic) has also been published to npm.org (v0.5.5) |
@dthornley Thank you. @picturae/mmmagic solve our issues with installation on node 20 (mac) |
Hello, I am trying to upgrade a project that uses mmmagic to node 20.
The following compile issues occur:
The text was updated successfully, but these errors were encountered: