Upgrading to Version 1.4.1 throws Error : Something went wrong installing the "sharp" module
See original GitHub issueDescribe the bug
I recently upgraded the @bubblewrap/cli
to the latest version using npm i -g @bubblewrap/cli
command.
Update bubblewrap cli
npm i -g @bubblewrap/cli
C:\Users\Naveed Ahmed\AppData\Roaming\npm\bubblewrap -> C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\bin\bubblewrap.js
+ @bubblewrap/cli@1.4.1
updated 1 package in 18.987s
Update Project
After updating bubblewrap/cli
when I tried to update my project using bubblewrap update
command, its throwing below error:
bubblewrap update
Something went wrong installing the "sharp" module
Cannot find module '../build/Release/sharp.node'
Require stack:
- C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\node_modules\sharp\lib\constructor.js
- C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\node_modules\sharp\lib\index.js
- C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\node_modules\@bubblewrap\core\dist\lib\TwaGenerator.js
- C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\node_modules\@bubblewrap\core\dist\index.js
- C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\dist\lib\cmds\update.js
- C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\dist\lib\Cli.js
- C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\dist\index.js
- C:\Users\Naveed Ahmed\AppData\Roaming\npm\node_modules\@bubblewrap\cli\bin\bubblewrap.js
- Remove the "node_modules/sharp" directory, run "npm install" and look for errors
- Consult the installation documentation at https://sharp.pixelplumbing.com/en/stable/install/
- Search for this error at https://github.com/lovell/sharp/issues
To Reproduce Steps to reproduce the behavior:
- Update existing verson of bubblewrap cli using command
npm i -g @bubblewrap/cli
- Run
bubblewrap update
command to update project - It will throw above error
Expected behavior The upgrade process should be very smooth and work without throwing any error.
Desktop (please complete the following information):
- OS: Windows 10
- Browser :Chrome
- Version 84.0.4147.89
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Something went wrong installing the "sharp" module #2517
The initial error message suggests webpack is looking for a file named 33c1e48f049ce3285905e286d212a201.node rather than sharp.node . D:\ ...
Read more >Error: Something went wrong installing the "sharp" module
I'm getting this error when I try to run gatsby develop, so far I've tried: npm install --ignore-scripts=false --verbose sharp; npm install ......
Read more >gatsby-transformer-sharp
gatsby-transformer-sharp Creates nodes from image types that are supported by the Sharp image ... Something went wrong installing the "sharp" module ...
Read more >How to fix "Something went wrong installing the "sharp ...
Upgrade to the latest Node.js from https://nodejs.org · Upgrade yarn - npm upgrade -g yarn · Clear the yarn cache - yarn cache...
Read more >If you get "Something went wrong installing the "sharp ...
Here is what I had to do on windows to make this work. Upgrade to the latest node from https://nodejs.org; Upgrade yarn -...
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 FreeTop 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
Top GitHub Comments
Created #259 to discuss reverting from sharp.
That’s annoying. Seems like
sharp
doesn’t have pre-compiled binaries for your architecture (and I wouldn’t expect people having to compile the dependencies themselves).Right now we’re considering reverting the move to sharp - It gives us SVG support, but also created #240, #258 and this issue.