Niels-IO / next-image-export-optimizer

Use Next.js advanced <Image/> component with the static export functionality. Optimizes all static images in an additional step after the Next.js static export.
413 stars 51 forks source link

Could not load sharp module error #207

Closed longgtruong closed 1 month ago

longgtruong commented 4 months ago

Hi i'm currently getting this error while building the static site "next-image-export-optimizer": 1.12.2

/home/runner/work/opendeur-monorepo/opendeur-monorepo/node_modules/next-image-export-optimizer/node_modules/sharp/lib/sharp.js:114
  throw new Error(help.join('\n'));
  ^

Error: Could not load the "sharp" module using the linux-x64 runtime
Possible solutions:
- Ensure optional dependencies can be installed:
    npm install --include=optional sharp
    yarn add sharp --ignore-engines
- Ensure your package manager supports multi-platform installation:
    See https://sharp.pixelplumbing.com/install#cross-platform
- Add platform-specific dependencies:
    npm install --os=linux --cpu=x64 sharp
- Consult the installation documentation:
    See https://sharp.pixelplumbing.com/install
    at Object.<anonymous> (/home/runner/work/opendeur-monorepo/opendeur-monorepo/node_modules/next-image-export-optimizer/node_modules/sharp/lib/sharp.js:114:9)
    at Module._compile (node:internal/modules/cjs/loader:1356:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
    at Module.load (node:internal/modules/cjs/loader:1197:32)
    at Module._load (node:internal/modules/cjs/loader:1013:12)
    at Module.require (node:internal/modules/cjs/loader:1225:19)
    at require (node:internal/modules/helpers:177:18)
    at Object.<anonymous> (/home/runner/work/opendeur-monorepo/opendeur-monorepo/node_modules/next-image-export-optimizer/node_modules/sharp/lib/constructor.js:10:1)
    at Module._compile (node:internal/modules/cjs/loader:1356:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)

Node.js v18.19.0
joshuabaker commented 2 months ago

Ultimately, locking sharp to 0.32 resolved the issue for us.

Possibly related issue: lovell/sharp#3994

Niels-IO commented 1 month ago

Hi @joshuabaker @longgtruong,

I just published a new version where I updated sharp to the latest version. Please reopen this issue, when the problem persists.