Open davegermiquet opened 4 years ago
@davegermiquet Iβm not an expert on yarn, but does using npm or updating yarn help? At least npm ships with its own copy of node-gyp.
@davegermiquet Iβm not an expert on yarn, but does using npm or updating yarn help? At least npm ships with its own copy of node-gyp.
I'll upgrade yarn now, is it a node-gyp version issue or a iltorb issue in compilation?
@davegermiquet I would be relatively sure that itβs the former.
@davegermiquet I would be relatively sure that itβs the former.
Ok. Same issue happens on latest version of yarn. Let me see if i can force a node-gyp version then.
@davegermiquet is it still happening?
I was able resolve the issue by doing the following:
Also may need to use resolutions feature with yarn for package.json depending on the dependencies
see below:
"resolutions": { "{package-name}/node-gyp": "^6.X.X" },
Hope this helps someone until the complete upgrades of python3
Problem:
Platform: Mac Os X (Version 10.14.6) Python Version: Python 3.7.4 Node version: v12.14.0 node-gyp: gyp info using node-gyp@5.0.5 (however i do have it set higher not sure why its choosing this one) Yarn: v1.16.0,v1.21.1
On a yarn install this happens:
How can we fix this issue?