building with turbopack breaks the app if you're using sharp as a dependency

[dooart]

this started happening after i added the --turbopack flag to next build:

⨯ Error: Failed to load external module sharp: 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
• 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

removing the flag makes the problem go away

[icyJoseph]

Interesting, are you using pnpm? is there a repository to look at?

If you are using pnpm, you have to run pnpm approve-builds, that'll add sharp to the be allowed to be built

[arvinxx]

hi @icyJoseph , we meet the same issue when run build with bun i

[pbochis]

using pnpm, running into the same issue after adding --turbopack to our builds.

pnpm approve-builds -> There are no packages awaiting approval

[macrozone]

Interesting, are you using pnpm? is there a repository to look at?

If you are using pnpm, you have to run pnpm approve-builds, that'll add sharp to the be allowed to be built

it doesn't build it nevertheless.

but yeah, it happens with pnpm and turbopack. not sure if it happens with npm and turbopack

[macrozone]

this is definitly a bug with turbopack and need to be adressed before it goes live

[Huh-David]

In my case the build process succeeds without errors. The build machine does not have any problems with turbopack. The production server throws 500s when trying to load something that requires sharp with the above mentioned error "Failed to load external module...".

[rgbjoy]

same @Huh-David !

[icyJoseph]

What's the minimal set of changes I need to do to a create-next-app to cause this error? Just install sharp explicitly?

[icyJoseph]

Looks like next@beta also fixes it? https://turbopack-sharp-500-m9d04341c-icyjoseph-dev.vercel.app/

[maichongju]

Downgrading sharp from 0.34.4 to 0.32.6 resolves this issue!

Can confirm this work but just a temp work around.

[icyJoseph]

Did you guys try with next@beta?

[maichongju]

I think next@beta is refering the nextjs 16. Which is a major version bump. Since this is for a production server, I don't want to risk encountering an unknown bug.

[icyJoseph]

oh, I thought you had capacity to deploy a preview branch and such. Yes, do not take unnecessary risks.