Keeping service-specific rules out of components
I wanted developers to describe an image in component code without having to learn a new URL format for every optimization service. The services still differ in their supported sizes, output formats, and cropping options, so a shared API needs to account for those differences.
I put URL generation and provider-specific rules in the shared core. For example, the Appwrite adapter checks the source URL and dimensions and reports unsupported cropping options explicitly. Framework integrations can use the same rules while keeping their own native component APIs.
I also consolidated the local optimization server used by the Angular, React, and Svelte integrations. That lets the integrations share routing and source-handling behavior, with tests covering the common implementation instead of maintaining separate server copies.
