You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Who and Why? I am working at Microsoft in tandem with a couple of our partners to bring ARM64 Windows support to Electron 6. Per nodejs/node#25998, this requires making a node-gyp release with these changes so that the release can be consumed downstream (in npm and thence in Node.js proper).
When? Electron 6 has a major release coming up, Electron 6 is based on Node.js v12, and it will take some time to get npm and Node.js and Node.js v12 to receive these changes, so I am really hoping for this to happen in the next three weeks or so.
How? Landing these three changes in the v5.0.0 release proposal, #1723, would be fine, and @joaocgreis has already made the request there.
If v5.0.0 needs more time due, perhaps, to requests for Python 3 and VS 2019 support, these three changes could (I believe) stand alone and so could be part of a v4.1.0 or even a v4.0.1 release.
I'm happy to help this happen any way I can and figured posting an issue would be a good start.
The text was updated successfully, but these errors were encountered:
Summary: Please cut a
node-gyp
release with full ARM64 support within the next few weeks so it can make it downstream to Electron 6.What changes? #1655, #1679, and #1739
Who and Why? I am working at Microsoft in tandem with a couple of our partners to bring ARM64 Windows support to Electron 6. Per nodejs/node#25998, this requires making a node-gyp release with these changes so that the release can be consumed downstream (in npm and thence in Node.js proper).
When? Electron 6 has a major release coming up, Electron 6 is based on Node.js v12, and it will take some time to get npm and Node.js and Node.js v12 to receive these changes, so I am really hoping for this to happen in the next three weeks or so.
How? Landing these three changes in the v5.0.0 release proposal, #1723, would be fine, and @joaocgreis has already made the request there.
If v5.0.0 needs more time due, perhaps, to requests for Python 3 and VS 2019 support, these three changes could (I believe) stand alone and so could be part of a v4.1.0 or even a v4.0.1 release.
I'm happy to help this happen any way I can and figured posting an issue would be a good start.
The text was updated successfully, but these errors were encountered: