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

Configure image rendering per project instead of always using pixelated

Open
  • Is something wrong?
#3,391 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@nighca is already working on this.

Since Aug 5, 2026.

Assessment

This issue has not been assessed yet.

Description

Background

XBuilder currently applies image-rendering: pixelated broadly through its image presentation component. This was introduced to preserve crisp scaling for pixel-art game assets (see #2214), but a global default degrades images that are not pixel art, including non-pixel-art game assets and project cover images.

Goal

Make image-rendering behavior configurable at the project level, while keeping pixel-art projects crisp and allowing normal interpolation where appropriate.

Proposed direction

  • Consolidate application image rendering through the img-rendering module.
  • Extend that module beyond the SVG font handling tracked by #3366 to own CSS image-rendering behavior as well.
  • Have editor rendering surfaces configure their image-rendering behavior through the module API, rather than relying on a hard-coded pixelated style in shared image UI.
  • Add project-level metadata expressing whether the project uses pixel-art visuals (or an equivalent rendering mode).
  • Use that project setting to configure editor image rendering through img-rendering.

The rendering module should remain the common boundary for both SVG-specific rendering work and CSS image-rendering policy, so all image consumers follow the same project-level behavior.

Scope

  • Identify and migrate image rendering paths that currently bypass img-rendering or hard-code image-rendering: pixelated.
  • Define and persist the project-level rendering-mode setting, including a compatibility default for existing projects.
  • Apply the configured mode consistently to editor content.
  • Ensure non-editor images, such as project covers, can use an appropriate non-pixelated rendering mode.
  • Add focused regression coverage for pixel-art and non-pixel-art rendering modes.

Related

  • #2214 introduced pixelated rendering to fix blurred small previews.
  • #3366 tracks editor SVG/image rendering and project-font support; this issue extends the same img-rendering boundary to CSS image-rendering policy.
Dominant language
TypeScript
Stars
70
Forks
59
Avg merge
2d 3h
Merged PRs (30d)
50

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 goplus/builder

All issues in goplus/builder

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.