Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`next/image` compatible component backed by Cloudflare Images

Open
  • Is something wrong?
#441 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
react, typescript
Domain
frontend

Research direction

Start by locating the Cloudflare Images binding pass-through in the native deploy code, then trace how shared components are packaged for the React, Vue, Svelte, and Solid SDKs. The issue proposes a cross-framework image component and optimizer but does not identify files or tests. Done means the component supports responsive sizing, format negotiation, lazy loading, and layout stability using the Cloudflare binding.

Written by the indexing model from the issue text.

Description

Problem

Void has no image component or image optimization endpoint. Pages apps ship full-size originals or hand-build srcset URLs, and there is no supported place to configure allowed widths, formats or remote hosts. Teams moving from Next.js on Vercel lose the next/image behavior they rely on: responsive srcset, AVIF/WebP negotiation, lazy loading, sizing without layout shift, and an optimizer that works without setup.

Cloudflare already provides the backend. The Images binding resizes and transcodes an image stream inside a Worker, and native Cloudflare deploys already pass an images binding declared under cloudflare through to the upload. Nothing in the SDK uses it yet.

Usage
// pages/index.tsx
import { Image } from '@void/react'; // the same component ships in @void/vue, @void/svelte and @void/solid

export default function Home() {
  return (
    <>
      <Image src="/avatars/void.png" alt="Void" width={64} height={64} />
    </>
  );
}

If this direction is appropriate, I would be happy to help implement the prototype.

Dominant language
TypeScript
Stars
402
Forks
32
Avg merge
11h 52m
Merged PRs (30d)
88

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/void

All issues in voidzero-dev/void

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.