-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sharp
optional binaries not included in .output
#1257
Comments
I couldn't get it working with |
This is a blocker for me right now, either I will remove nuxt-image or I will find a workaround with pnpm. It is very annoying |
The latest update (1.4.0) shoots my server build to 50MB+ from ~12-ishh. Is this intentional/desirable? Seem exorbitant. I was unaware that the the plugin included resizing functionality. Is there an option to exclude the "sharp" dependency from the server bundle and have it installed in the deployment server environment? Thanks. |
Has anyone found a workaround with pnpm? This is also a blocker for me at the moment. UPDATE: added sharp 0.33.3 (or higher) to overrides and it works correctly. |
This is the only fix that worked for me, everything else described even using the latest nuxt image version failed when deploying a nuxt project built on m1 to a linux x64 server. |
I just moved to a monorepo setup and had to include
|
Reproduction
Open: http://localhost:3000/provider/ipx
Sharp binaries, bundled as
@img/sharp-*
, are not included in generated.output
. Tests may pass, because of module resolution. We need to isolate.output
(or delete root projectnode_modules
, as with reproduction), as it should be done in production.Related: lovell/sharp#4000 (cross architecture build)
Related: #1237, #1210 (either cross architecture build or isolating .output)
Related: #1253 (both cross architecture build and isolating .output)
Workaround before this gets fixed: downgrade
sharp
to0.32.6
via your package manager.The text was updated successfully, but these errors were encountered: