The specified module could not be found
See original GitHub issueI’m attempting to upgrade my app from Electron v3 to v7. macOS and Linux works fine, but I’m getting the following errors on Windows:
32-bit:
Uncaught Error: The specified module could not be found.
\\?\C:\Program Files\Tidepool Uploader\resources\app.asar.unpacked\node_modules\lzo-decompress\prebuilds\win32-ia32\electron.napi.node
64-bit:
Uncaught Error: The specified module could not be found.
\\?\C:\Program Files\Tidepool Uploader\resources\app.asar.unpacked\node_modules\lzo-decompress\prebuilds\win32-x64\electron.napi.node
I’ve found some threads relating to that error appearing when some .dll’s cannot be found. I’m still using the same .dll’s that worked under Electron v3, so I thought it may be due to https://electronjs.org/docs/tutorial/using-native-node-modules#a-note-about-win_delay_load_hook, but my understanding is that win_delay_load_hook
is handled by node-gyp-build
?
The module’s source code can be found here: https://github.com/tidepool-org/lzo-decompress/tree/update-deps
Notes:
- I’ve updated to the latest versions of
prebuildify
,node-gyp-build
andnapi-macros
. - I’m using
prebuildify --napi
andprebuildify --arch=ia32 --napi
to generate the prebuilds - Obviously the .node files in question are actually there
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (11 by maintainers)
Top Results From Across the Web
How To Fix The specified module could not be found
Fixes for The specified module could not be found · Fix 1: Run the SFC scan · Fix 2: Update your device drivers...
Read more >4 Ways to Solve the Specified Module Could Not Be Found
The specified module could not be found error is a DLL error. It usually shows on the Windows startup or warming up. This...
Read more >The specified module could not be found | 3 Ways to Fix It
"The specified module could not be found" error often occurs on Windows startup or when launching a particular program.
Read more >7 Ways To Fix “The Specified Module Could Not Be Found” Error
“The specified module could not be found” is a common error that usually occurs when your system tries to access missing DLL files....
Read more >5 ways to Fix "The specified module could not be found"
How to Fix “The specified module could not be found” on Windows 11/10? · 1. Install or Repair Microsoft DirectX · 2. Download...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was thinking maybe just another footnote in the options table, next to the
--napi
flag. As in, “***** Usingprebuildify --napi
will only support Electron v3 if not targeting a specific Electron or Node version. Useprebuildify -t 8.14.0 --napi
to produce a runtime-agnostic prebuild that works in both Node v8 (and higher) and Electron v4 (and higher).”Breaking the footnotes into a FAQ/Caveats section could also work.
I remember that
leveldown
had issues with electron v3 and we ended up requiring a minimum of electron v4, and it was related to the delayed load hook mess. Lemme see if I can find it in GH history.