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
I have raised an issue (electron/node-abi#103) with node-abi to investigate a fix, but I don't know if they will be willing to do anything
When building for electron 11, prebuild is using the headers for v11.0.0-beta.11. However due to some changes introduced in v11.0.0-beta.12, these binaries can be incompatible with other versions of electron 11.
I have confirmed this in that library by trying to run builds produced directly from node-gyp using both v11.0.0-beta.11 and v11.0.0-beta.12 headers in various versions of electron 11. I also manually applied this patch onto my cached v11.0.0-beta.11 headers to confirm it is the snippet at fault.
The fix is simply to use a different version of the headers than node-abi says. Hopefully this is a one-off and wont be a recurring issue in future electron versions
The text was updated successfully, but these errors were encountered:
This is a snippet of a discovery found in serialport/node-serialport#2191 (comment)
I have raised an issue (electron/node-abi#103) with node-abi to investigate a fix, but I don't know if they will be willing to do anything
When building for electron 11, prebuild is using the headers for v11.0.0-beta.11. However due to some changes introduced in v11.0.0-beta.12, these binaries can be incompatible with other versions of electron 11.
I have confirmed this in that library by trying to run builds produced directly from node-gyp using both v11.0.0-beta.11 and v11.0.0-beta.12 headers in various versions of electron 11. I also manually applied this patch onto my cached v11.0.0-beta.11 headers to confirm it is the snippet at fault.
The fix is simply to use a different version of the headers than node-abi says. Hopefully this is a one-off and wont be a recurring issue in future electron versions
The text was updated successfully, but these errors were encountered: