-
Notifications
You must be signed in to change notification settings - Fork 135
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 error on deployment #292
Comments
Also I tried running the failling command it give more info about the error
|
Error seems pretty clear |
@sladg thank you for you time! here is the same run failling on
|
here is the log for the failling sub command on
|
when I replace "18" by "18.0.0" the command runs well. the change is needed just here |
This seems like sharp-related thing. Can you try installing libvips yourself instead of relying on Sharp? Check out https://formulae.brew.sh/formula/vips. I would encourage you to open issue on sharp's repo, it seems like they are using libvips version which was not pre-compiled for ARM :/ |
I'm on Windows WSL 2 Ubuntu (x86_64), I've installed Am I the only one not being able to deploy my nextjs app on a standard x86 linux system ? Is everyone using open-next on an arm64 M1 macbook thus being able to get the arm64 libvips straight from brew cmd ? thank you for your time |
Well, it seems WSL-related I think. Either way, I would recommend changing the @khuezy would it make sense to pre-package whole lambda code so it's just copy-paste? I went with that approach in https://github.com/sladg/imaginex-lambda/tree/master as it was too much headache to deal with different OS-es and settings, so prepackaging everything and uploading ready code to Lambda was easiest. |
"replacement of shitty build-in NextJS image optimizer." lol Yea, let's try to use your |
I've found a quick working workaround for the time being like this: $ npm install --arch=arm64 --platform=linux --target=18 --libc=glibc --prefix="/home/nemesis/workspace/app/apps/web/.open-next/image-optimization-function" [email protected] --sharp_libvips_binary_host=https://github.com/lovell/sharp-libvips/releases/download/
added 51 packages in 7s
10 packages are looking for funding
run `npm fund` for details that could be a quicker fix for open-next |
@khuezy it's okay-ish, but there is overhead of starting up Next on image request. Also, trying to separate it efficiently and/or handle dependencies is rather painful. The API is rather simple so recreating in Python with minimal overhead seemed like win-win. |
Since the process is async and result is cached at CDN, the extra latency shouldn't be a big deal. |
Hello I encounter this error when deploying a simple nextjs app
Thank you
The text was updated successfully, but these errors were encountered: