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

SVG Playground: add an SVG to SolidJS component converter

Closed
#178 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start by comparing lib/svg/angular.ts and lib/svg/svelte.ts, then check how components/svg/svg-output.tsx picks a converter and where a new tab would be added. The brace escaping and xlink:href to href handling live in lib/icons/export.ts, so read that before writing the Solid output. Done means the output type-checks with solid-js under tsc --strict and a unit test in lib/svg/ covers a small SVG.

Written by the indexing model from the issue text.

Description

area: ui difficulty: easy enhancement good first issue

Summary

Add a SolidJS converter tab to the SVG Playground, next to the Vue, Svelte and Angular converters.

Where to look

  • components/svg/svg-output.tsx
  • lib/svg/angular.ts and lib/svg/svelte.ts: converters to copy
  • lib/icons/export.ts: the Solid icon export (brace escaping, xlink:href to href)

Acceptance criteria

  • Output type-checks with solid-js (tsc --strict in a scratch folder).
  • A unit test in lib/svg/ covers a small SVG.

Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build. See CONTRIBUTING.md and the first contribution walkthrough.

Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.

Dominant language
TypeScript
Stars
11
Forks
3
Avg merge
3h 49m
Merged PRs (30d)
81

Getting set up

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 yakew7/DesignHub

All issues in yakew7/DesignHub

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.