-
Notifications
You must be signed in to change notification settings - Fork 66
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 fails on Windows with Electron 11: 'napi_is_detached_arraybuffer': identifier not found #63
Comments
Thanks for the details, will investigate. |
This compile error is caused by a weird build environment / incompatibility of electron-rebuild. I haven't located the exact issue, but building from source should not be required at all. I've added new instructions on workarounds here: https://github.com/journeyapps/node-sqlcipher/blob/3870217c1245dd4253e2bac2ea8d1d12a8c4a2b6/README.md#usage-with-electron-forge--electron-rebuild |
This results in the following error for me:
I think it's because of |
Yes, unfortunately electron-rebuild doesn't have an option to only exclude certain modules. You'll have to include all modules that do need to be rebuilt on the |
Any idea how I can tell what modules those are? I don't see any way in electron-rebuild to list them. |
I don't know of an accurate way, but you can search for package.json files that contain a reference to You should also check if you have other logs indicating why you don't have a server running on http://localhost:3000. |
I tried adding everything that references node-gyp to onlyModules (except node-sqlcipher) but I get the same error. I would also except there to be more logs why the localhost server isn't running, but I can't find a way to show more. It just seems to fail silently. I guess this is more of a electron-rebuild problem. I'll wait for compatibility with electron-rebuild, not sure I can fix this on my end. |
Using version 5.0.0 with Electron 11.0.3 and Node 12.20.1 on Windows 10
I'm building it with electron-forge.
Anything I can try?
The text was updated successfully, but these errors were encountered: