Skip to content

Make sharp usage forward-compatible with 0.35 - #647

Merged
mikelittle merged 1 commit into
masterfrom
fix/sharp-0.35-forward-compat
Aug 12, 2026
Merged

Make sharp usage forward-compatible with 0.35#647
mikelittle merged 1 commit into
masterfrom
fix/sharp-0.35-forward-compat

Conversation

@mikelittle

Copy link
Copy Markdown
Contributor

Unblocks the sharp 0.35 bump (#637).

sharp 0.35 removes the failOnError option and no longer exposes
OutputInfo off the default import, which breaks tsc. Both changes here
are backward-compatible with the current 0.34.5, so this can merge first
and get reviewed on its own; #637 then only needs its package bump.

🤖 Generated with Claude Code

Use `failOn: 'none'` (successor to the removed `failOnError` boolean) and
import `OutputInfo` as a named type instead of off the default import.
Compiles against both 0.34.5 and 0.35, so it can land ahead of the sharp
bump (#637) to unblock that PR's CI.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@wisyhambolu wisyhambolu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@mikelittle
mikelittle merged commit 8bf6ab2 into master Aug 12, 2026
4 checks passed
@mikelittle
mikelittle deleted the fix/sharp-0.35-forward-compat branch August 12, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants