No loader is configured for ".node" files: node_modules/sharp/build/Release/sharp-darwin-arm64v8.node about sharp HOT 5 CLOSED

No loader is configured for ".node" files

It looks like you're using some form of code bundler, please see https://sharp.pixelplumbing.com/install#bundlers

I am not using latest version because it breaks my deployment on Vercel. Instead, I am using version 0.32.6 as a workaround that was suggested by multiple people

This was due to a bug in Next.js - please upgrade to Next.js version 14.1.0 or later.

from sharp.

No loader is configured for ".node" files

It looks like you're using some form of code bundler, please see https://sharp.pixelplumbing.com/install#bundlers

I am not using latest version because it breaks my deployment on Vercel. Instead, I am using version 0.32.6 as a workaround that was suggested by multiple people

This was due to a bug in Next.js - please upgrade to Next.js version 14.1.0 or later.

Hi lovell! Thanks for your response. I am using Astro.js but don't have any Vite file (which is the bundler that i think that Astro is using. How do i go about this? I'm a little new to this stuff so any help and direction i can get is great.

In regards to your second comment about upgrading Next.js, how and why would I do that since I am on Astro? Or is there an Astro-specific fix instead?

Thanks again for your help.

from sharp.

Sorry, I saw Vercel and misinterpreted your initial comment as relating to Next.js. 😅

My understanding of Astro is that it bundles sharp for you and should "just work".

Are you trying to do something extra with sharp beyond Astro's built-in image optimisation? If so, Astro exposes the underlying Vite config at https://docs.astro.build/en/reference/configuration-reference/#vite so the info at https://sharp.pixelplumbing.com/install#vite should help.

from sharp.

Hey, as an update:

Still no luck on this so I've submitted an issue on Astro's repo for this. withastro/astro#10297

In that issue submission, I created a minimum reproduction of the issue with a public link to the repo and a public link to it hosted on Vercel.

Hopefully we're able to get a solution.

from sharp.

I agree with the comments on withastro/astro#10297 that this will be due to an out-of-date version of @vercel/nft. I'll close this issue and we can track the required change to Astro at withastro/astro#10297

from sharp.