The is a small but powerful lever for developers. By choosing the right level of strictness, you can balance the need for high-volume processing with the necessity of server stability and output quality. For most production environments, starting with warning is a best practice to ensure your image pipeline remains "sharp" and reliable. Files | Directus Docs
Fails on any warning emitted by the decoder, ensuring maximum strictness. Historical Evolution sharp failon option
Understanding the Sharp failOn Option: Managing Image Processing Reliability The is a small but powerful lever for developers
// Sharp specific flag for incomplete data if (info.truncated) throw new Error('Image is truncated (incomplete data)'); Files | Directus Docs Fails on any warning
Based on the terminology, this request likely refers to the image processing library (for Node.js). Users often look for a way to make Sharp "fail" or throw an error when processing certain images (e.g., invalid formats or truncated files), rather than returning a processed result or silently handling the error.