-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 module fails to load on linuxmusl-x64 runtime
during Next.js build on Fly.io
#4236
Comments
The "Cannot read properties of null (reading 'matches')" error suggests you might be using peer linking - see npm/cli#4367 |
@lovell, thx for the fast reply, these logs where from my local machine and not Fly.io. It was a mistake and mixed environments. Right now I try to get the logs from Fly.io. |
Currently, when trying to run the diagnostic commands on Fly.io, the process is being killed due to an out-of-memory issue. I’ve reported this memory issue to the |
@lovell, after some research, we found out that
|
Thanks for the updates, the install log looks good (assuming run on musl-based Linux), I'm not sure what might have caused the original problem. You're dealing with a multi/cross-platform installation so pnpm is a good choice compared with the current state of npm, especially when lockfiles are involved. Perhaps consider defining custom supportedArchitectures if not already doing so. If you're able to reproduce and also provide steps for someone else to reproduce then happy to help further. |
@ProchaLu Were you able to make any progress with this? |
Possible install-time or require-time problem
You must confirm both of these before continuing.
Are you using the latest version of sharp?
sharp
as reported bynpm view sharp dist-tags.latest
.Version
0.33.5
If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of
sharp
that is not the latest,please open an issue against that package instead.
Are you using a supported runtime?
^18.17.0 || ^20.3.0 || >=21.0.0
If you cannot confirm any of these,
please upgrade to the latest version
and try again before opening an issue.
Are you using a supported package manager and installing optional dependencies?
--include=optional
--no-optional=false
If you cannot confirm any of these, please upgrade to the latest version of your chosen package manager
and ensure you are allowing the installation of optional or multi-platform dependencies before opening an issue.
What is the complete error message, including the full stack trace?
The error message I encountered during the build process while deploying a Next.js
v15.0.0-canary.171
app to Fly.io using Docker is as follows:What is the complete output of running
npm install --verbose --foreground-scripts sharp
in an empty directory?What is the output of running
npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp
?I need to run this command the same Fly.io Docker Linux Alpine env. Will update
Additional Information
After encountering this error, I attempted to redeploy the application an hour later. The error was no longer present, and the deployment worked without any issues. I was not able to reconstruct the error after this.
The text was updated successfully, but these errors were encountered: