v0.29.0 Windows x64: Cannot find module '../build/Release/sharp-win32-x64.node'
See original GitHub issueHi,
Pretty sure I’ve followed all the steps provided. I’m using yarn add sharp
. I’ve also tried using npm -i sharp
and other variations with me specifying the platform / arch as well.
This is the installed module:
And the actual error:
Specs:
I don’t really know where to go from here with this.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Something went wrong installing the "sharp" module #1621
Gridsome v0.7.23. Error: Something went wrong installing the "sharp" module. Cannot find module '../build/Release/sharp-win32-x64.node'
Read more >How do I resolve "Cannot find module" error using Node.js?
Using npm install installs the module into the current directory only (in a subdirectory called node_modules ). Is app.js located under ...
Read more >cannot find module [Node npm Error Solved] - freeCodeCamp
I'm getting the error because I'm trying to import the freeCodeCamp icon from the react-icons package, which I don't have installed. import { ......
Read more >Installation - High performance Node.js image processing
Prebuilt sharp and libvips binaries have been provided for macOS on ARM64 since sharp v0.29.0. Cross-platform. At npm install time, prebuilt binaries are ......
Read more >Technical Support - PDFTron Community
Product: PDFNet-node Product Version: 9.2.0-1 Please give a brief summary ... (Linux x64), I first get an error named “Cannot find module '....
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
Thanks for reporting this. Glad we got it fixed before the whole (Windows) world came beating at the door with the same problem.
Had the same problem and fixed by manually deleting files from the
_prebuilds
directory. Glad I found this issue. Thanks @webnoob and @lovell.