我为你的图标构建了“包管理器”(一个源 → 一致的输出)。

2作者: Theryston5 个月前原帖
这个周末,我开始构建 Iconoma,因为我在多个项目中遇到了同样的问题: 图标慢慢变成了一个杂物抽屉。 随机的 SVG 图标,尺寸不一致,填充效果奇怪,命名各异,优化规则不同,每个应用/团队最终都要重新解决相同的清理工作。结果就是无数小的 UI 切割造成的死亡。 我的愿景是:图标应该是无聊的基础设施——一个真实的来源,确定的输出,零“为什么这个图标不同?”的惊喜。 ## Iconoma 的功能 - 导入和组织图标,确保命名和标签的一致性 - 使用可自定义的配置运行 SVGO(这样你的规则得以执行,而不是“随便上一个人做的”) - 从同一来源自动生成目标: - 优化后的 SVG - React 组件 - React Native 组件 - 保持可复现性(这样你可以检测到源文件的变化,并仅重建所需的部分) 你可以这样尝试:npx @iconoma/cli studio ## 我认为这很重要的原因 当图标没有标准化时,你将永远付出代价:UI 不一致、PR 反复、奇怪的渲染错误,以及永无止境的“清理”任务。Iconoma 是我试图将这些成本降到接近零的努力。 ## 我希望得到反馈的内容 - 工作流程:CLI 优先 + Studio——这是否符合团队实际管理图标的方式? - 除了 SVG/React/RN 之外的必备目标(Vue?Svelte?Flutter?图标字体?) - 你最大的图标痛点是什么(对齐?颜色映射?命名?审查流程?) 如果这听起来有用,我很想知道什么会让你觉得这是一个“是”的选择(或者为什么不是)。 ## 链接: Github: https://github.com/theryston/iconoma 网站: https://iconoma.org
查看原文
This weekend I started building Iconoma because I kept hitting the same problem across projects:<p>Icons slowly turn into a junk drawer. Random SVGs with inconsistent sizes, weird fills, different naming, different optimization rules, and every app&#x2F;team ends up re-solving the same cleanup work. The result is death by a thousand tiny UI cuts.<p>My vision: icons should be boring infrastructure — one source of truth, deterministic outputs, zero “why is this icon different?” surprises.<p>## What Iconoma does<p>- Imports and organizes icons with consistent naming + tags - Runs SVGO with your customizable config (so your rules are enforced, not “whatever the last person did”) - Generates targets automatically from the same source: - optimized SVG - React components - React Native components - Keeps things reproducible (so you can detect when a source changed and rebuild only what’s needed)<p>How you try it: npx @iconoma&#x2F;cli studio<p>## Why I think this matters<p>When icons aren’t standardized, you pay forever: UI inconsistencies, PR churn, weird rendering bugs, and constant “cleanup” tasks that never end. Iconoma is me trying to make that cost go to ~zero.<p>What I’m looking for feedback on<p>- The workflow: CLI-first + Studio — does this match how teams actually manage icons? - Must-have targets beyond SVG&#x2F;React&#x2F;RN (Vue? Svelte? Flutter? Icon fonts?) - Your biggest icon pain point (alignment? color mapping? naming? review process?)<p>If this sounds useful, I’d love to hear what would make it a “yes” for you (or why it wouldn’t).<p>## Links:<p>Github: https:&#x2F;&#x2F;github.com&#x2F;theryston&#x2F;iconoma Web: https:&#x2F;&#x2F;iconoma.org