Can we skip process.exit(1) from sharp error try/catch ?

[sytolk]

What are you trying to achieve?

To let the user handle error better this line can be skipped: https://github.com/lovell/sharp/blob/master/lib/sharp.js#L23
I'm using sharp in native Electron app that needs to be running never mind that sharp have installation problems on some platforms like:

na@na-x1 ~/Desktop $ ./tagspaces-linux-x86_64-4.0.1.AppImage 
Tagspaces WS: Something went wrong installing the "sharp" module
Tagspaces WS: libvips-cpp.so.42: cannot open shared object file: No such file or directory
Tagspaces WS: Possible solutions:
Tagspaces WS: - Install with the --verbose flag and look for errors: "npm install --ignore-scripts=false --verbose sharp"
Tagspaces WS: - Install for the current runtime: "npm install --platform=linux --arch=x64 sharp"
Tagspaces WS: - Consult the installation documentation: https://sharp.pixelplumbing.com/install

Have you searched for similar questions?
yes
Are you able to provide a minimal, standalone code sample that demonstrates this question?
yes

[lovell]

Yes, we should alter this logic to throw an Error instead (it was only changed recently via commit 6c2e6c5 and I can't remember what the reason for this was, if any).

[sytolk]

as temporary fix for this we can use sharp version 0.28.3 it works as expected. Thanks!

[lovell]

v0.29.2 now available with the fix for this.