`sharp` module preventing the dev server from being started.

zochh

2 months ago

14

C:\Users\<user>\Desktop\code\texturepacksmc\payload\node_modules\payload-webp\node_modules\sharp\lib\sharp.js:37
  throw new Error(help.join('\n'));
        ^
Error:
Something went wrong installing the "sharp" module

The specified procedure could not be found.
\\?\C:\Users\<user>\Desktop\code\texturepacksmc\payload\node_modules\payload-webp\node_modules\sharp\build\Release\sharp-win32-x64.node

• 

  notchr

  2 months ago

  @zochh Sharp has caused a few issues for folks in the past

  
  

  
  

  What operating system are you installing Payload on?

  
  

  
  

  Looks like Windows

• 

  zochh

  2 months ago

  Windows 11; it just started doing that

• 

  notchr

  2 months ago

  Did you update node or changed versions?

• 

  zochh

  2 months ago

  Nope, updated node to v20 from v19 (cant remember subversions) last week, and it worked last week after updating too

• 

  notchr

  2 months ago

  So sharp is a module that generally compiles via node-gyp on installation. This issue, among others, is typically because of a change in node.js versions and the version support with Sharp

  
  

  
  

  You can try to clear your npm cache and rebuild your repository node modules

  
  

  
  

  I think it's

  
  

  
  

  npm cache clear

  
  

  
  

  npm rebuild --verbose sharp

  
  

  
  

  If that doesn't work, I have some other ideas

• 

  zochh

  2 months ago

  same for yarn?

  
  

  
  

  I use yarn instead of npm

• 

  notchr

  2 months ago

  Yeah I would try to clear the yarn cache and then attempt a rebuild, I'm not sure if the syntax is the same

• 

  zochh

  2 months ago

  cahce clean worked, rebuild didnt

  
  

  
  

  looking up for the yarn sytanx

• 

  notchr

  2 months ago

  hmmm

  
  

  
  

  yarn rebuild sharp

  
  

  
  

  i think should work

• 

  zochh

  2 months ago

  Command

  rebuild

  not found

• 

  notchr

  2 months ago

  https://yarnpkg.com/cli/rebuild
• 

  zochh

  2 months ago

  whoops, having yarn 1.xx

• 

  notchr

  2 months ago

  @zochh Maybe a yarn update will resolve the module issue'

• 

  zochh

  2 months ago

  yarn upgrade broke the package.json haha. Reverted the changes- going to use npm for the payload bit

  
  

  
  

  Heya, sorry got caught up in work irl

  
  

  
  

  and updated yarn to v2, and try rebuilding

  
  

  
  

  and when running the dev server same error

  
  

  
  

  I've figured the issue out;

  
  

  Needed to add this to

  package.json
  

    "resolutions": {
      "sharp": "latest"
    }

  
  

  and needed to remove the webp plugin