FAQ and troubleshooting

Answers reflect the published packages: [email protected] (components) and @moewolf/[email protected] (CLI, experimental). Each answer points at the relevant page.

Components and rendering

An icon is not found. Import from moe-icons/react or moe-icons/vue only. The published package does not export moe-icons/free/... or per-style-group paths.

The icon is huge or 300×150. React components have no default size. Pass width and height.

The Vue icon ignores width/height. Vue components add moe-icon w-6 h-6. With Tailwind those classes can win; override the class or use CSS. See Vue.

Colour has no effect. The SVG uses stroke="currentColor" / fill="none". Set a parent color, or override color/stroke/fill. Hard-coded fill in your CSS wins.

Can I use two styles of the same icon? Not from the published package (single style). Download each Free group's SVG from the search page. The CLI proxy path is not yet consumable; see CLI release status.

Package and dependencies

moe-icons added React/Vue to my project.[email protected] lists react, react-dom and vue as non-optional peers and as dependencies for react/vue. Dedupe or align versions.

ReactIconProps is not exported from moe-icons/react. Import type helpers from the package root:

import type { ReactIconProps, VueIconProps } from 'moe-icons';

React warnings

Invalid DOM property 'stroke-linecap'. The published React components pass kebab-case SVG attributes. React warns but renders correctly. See React.

Accessibility

The icon is read as an image with no name, or ignored. The components do not add role/aria-hidden. For meaningful icons pass aria-label (and role="img"); for decorative icons pass aria-hidden="true". See Usage.

Website search

No icons appear. The icon browser may be disabled in that deployment (The new icon browser is not enabled...).

A style group shows a lock. It is Pro-only or your entitlement is inactive. See Free vs Pro.

There is no "copy ID" button. Correct. Copy the generated code, or read the ID from the card. See Website search.

A bitmap variant is missing / download fails. Pick a supported format/size; a locked or expired entitlement returns 403. Reload after signing in.

CLI

Why does moeicons install free fail with 404? The 0.0.1 release requests a descriptor checksum asset that the v0.0.17 GitHub release does not publish. See CLI release status.

Why do generated proxies fail to import? They import moe-icons/free/... / moe-icons/pro/..., which [email protected] does not export. Use the component package or assets until this is fixed.

Does the CLI have doctor, recover or update? No. Those are not part of 0.0.1.

unknown field "icons" in theme. Per-theme icons is unsupported; use the top-level icons list. See Configuration.

style group "moe-colored" is not available in free tier. The 0.0.1 bundled catalog treats moe-colored as Pro-only. Use moe-outline, moe-lite-outline or moe-solid.

Pro

How do I get Pro? Buy on moeicons.com/pricing, then return to the site and wait for your account to become active. See Free vs Pro.

Can I use Pro icons in my own product? Yes, within the license shown at checkout: you may integrate the icons in products you own or control. You must not put account credentials in front-end source, and you must not redistribute the icons as a standalone resource library. See Free vs Pro and the license text for the exact terms.

Assets and deployment

A downloaded SVG is a 404 after deploy. The path depends on where you copied the file. Fix the src/base path; the repo does not manage your hosting layout.

Bitmap 404. Bitmap icons are Pro-only and need the exact format/imageSize; confirm the variant exists on the search page.

Tailwind not applied. No stylesheet ships; moe-icon is an unstyled marker class (Vue adds w-6 h-6). Use explicit width/height or your own CSS.

Animation

The icon files are static SVG with no animation metadata. Animate them with your own CSS or JavaScript. See Introduction.