Menu
Theme

Years I contributed:2026Developer tools · Open source

DeSource Image

Runtime image optimization for Angular, React, and Svelte, inspired by the developer experience of Nuxt Image.

My role
Creator & key maintainer
Context
Personal initiative · DeSource Labs · Open source
Explore the project

I started DeSource Image while building an Angular application with server-side rendering. I loved working with Nuxt Image and wanted the same experience: choose a source, describe the output in component code, and let the image tooling handle delivery.

After researching the alternatives, I could not find the combination I wanted for that Angular project. I built it, then extended the approach to React and Svelte, with shared image rules and support for a wide range of optimization services.

Built with
TypeScriptAngularReact / Next.jsSvelte / SvelteKitSSRIPX
  • A familiar image workflow across frameworks

    Built native framework integrations around a shared core so developers can control quality, format, crop, and responsive sizes in component code.

  • Runtime optimization

    Supported local and remote sources, responsive output, placeholders, and local IPX routes without requiring developers to export image variants by hand.

  • Choice of optimization service

    Added provider integrations and deployment-aware selection, with explicit overrides. Expanding service support remains part of the project’s direction.

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.

My independent practice

My independent work spans client collaborations and my own developer tools. I established my business in January 2025, building on earlier project work. I handle architecture, implementation, and delivery; when a project needs more capacity, I can bring designers and engineers through DeSource Labs.

Career timeline January 2025–present

  1. Individual Entrepreneur / Software Development Consultant

    January 2025–present

Broader responsibilities

Hands-on product development and technical consulting through my own business.

  • Develop web applications, front-end systems, and integrations for clients, from technical planning through implementation and handover.
  • Work on software architecture, backend and infrastructure planning, AI integrations, and blockchain applications.
  • Create and maintain developer tools including Phone Mask, DeSource Image, Context7 Widget, and Browser AI.
Full CV
Start a conversation

What are you
working on?

An engineering role, a product to build, or a technical problem to work through. I’d like to hear about it.