Icon Studio: export the icon as a Preact component
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 87/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in lib/icons/export.ts and follow the existing React export pattern; then read lib/icons/export.test.ts to see how output is tested. Add the Preact option to the export panel with copy and download, supporting both class and className while spreading props onto the SVG. Done when the generated component type-checks with preact and a unit test covers its output.
Written by the indexing model from the issue text.
Description
Summary
Add a Preact component export next to React, Vue, Svelte, Angular, Solid, Qwik, Lit, Astro and React Native.
Where to look
lib/icons/export.ts: the React exportlib/icons/export.test.ts
Behaviour
- Use
himports or the automatic JSX runtime; spread props onto the<svg>; keepclassandclassNameboth working.
Acceptance criteria
- The Preact tab appears in the icon export panel with copy and download.
- The output type-checks with
preactin a scratch folder. - A unit test covers the output.
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 (CI fails on unformatted files, so pnpm format first). 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
- 4h 4m
- Merged PRs (30d)
- 74
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/DesignHub
-
area: projects difficulty: medium enhancement help wanted performance v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
area: backgrounds difficulty: hard enhancement help wanted performance v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
dependencies difficulty: easy enhancement help wanted v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area: mockups area: social difficulty: medium enhancement help wanted performance v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
area: ui difficulty: medium enhancement help wanted performance v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in yakew7/DesignHub
Similar issues
-
a10y a10y-audit ai-driven-qa claude
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
linagora/twake-directory-manager#219 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Pulse v7: buildPreferencesFromTelos() bypasses telosSectionOrFile(), renders empty on unified-TELOS installsPossibly taken @zephyr91 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2393 ·
Maintainers usually reply within 4 days