-
Notifications
You must be signed in to change notification settings - Fork 7
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
Build error when falling back to source when installing via yarn. #26
Comments
There are probably outdated deps (node-pre-gyp) in this package. Should be no problem on node.js < v15 though. |
It's really odd. I just tried installing node It just seems to have problems installing when in combination with the other mods. Have you ever seen any such behavior? |
I just forked this and replaced I don't have time right now to test backwards compatibility with older node versions, but this does seem to be a solution in my specific case. |
Thanks for the solution, I'll look into that. |
I'm experiencing a strange error with
murmurhash-native
when it is installed viayarn
and is forced to be built from source usingnode-pre-gyp
.I am running on OSX Big Sur, via the latest update of
nvm
, and node16.13.1
with yarn1.22.15
. But this same exact error occurs on my docker container when building via CircleCI, so I know it is not platform specfic.If I nuke
yarn.lock
andnode_modules
and runyarn
I get the following error:If I create a new project, with a new
package.json
and only installedmurmurhash-native
, then yarn is able to install it correctly.If I install the package independently using the command
npm i murmurhash-native --build-from-source
, then it installs correctly. So I know I am able to build it on my computer.These problems started when I upgraded to node 16, since it is the new LTS build. I don't quite know what to make of it.
Thank you for your time. :)
Here are the relevant portions of my
package.json
The text was updated successfully, but these errors were encountered: