Closed Dirk- closed 1 week ago
Sorry, I think I missed this one at the time. Is this still a problem? I notice the linked repo readme says: "Updated a few packages, including quasar, electron and sharp -> now it works ¯(ツ)/¯".
Sorry, I think I missed this one at the time. Is this still a problem? I notice the linked repo readme says: "Updated a few packages, including quasar, electron and sharp -> now it works ¯(ツ)/¯".
Thanks for asking, but the problem is gone now, indeed :)
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
.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?
There is no error message when I start the program, but sharp is not there. I included the build log instead.
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
?What I did
I put up a sample project to demonstrate the issue. I managed to get Quasar work with yarn v4. I edited the electron-builder options in
quasar.config.js
according to the sharp instructions, I used thesupportedArchitectures
option in.yarnrc.yml
. Since then the error shown when starting the packaged app is gone, but sharp does nothing. I noticed YN0007 in the build log above, but I do not know how to overcome this.The dev version runs the short sharp test fine.
There is some information on vite handling on the Quasar website which can possibly combined with the sharp information, but I don't know how.
I only see instructions on how to unpack or exclude sharp from bundling, but how will it get into the packaged app?
I am sure I am just missing a trivial thing, but I do not know which...