Q. My icon import cannot be resolved
Check the exclusion lists linked from the Introduction when an icon is unavailable. These lists document sources that the QIcon path converter cannot represent correctly.
Check that the folder name matches the current package output. The Icon Finder and Introduction page list the generated icon sets and import paths.
The package keeps at most the current and immediately preceding major version of an icon family. If an older versioned import path was retired, use the Icon Finder and release notes to select a shipped path and update the import.
Q. My icon renders as a square or looks incomplete
Some upstream SVGs use features that cannot be flattened safely, such as mask, use, gradients, filters, or malformed view boxes. Known issues are documented on the Introduction page.
Unsupported icons are excluded, with names and reasons recorded in each affected icon set’s README. If an exported icon still looks wrong, report its icon-set folder, export name, source SVG behavior, and a screenshot. To use excluded artwork, load the original upstream SVG through QIcon’s img: support.
Q. My icon color does not change
Some icon sets preserve fixed colors by design. This is common for flags, emoji, and brand assets. Monochrome icon sets are usually converted to currentColor.
Q. TypeScript cannot find declarations
Make sure you are importing from a shipped folder and that your package manager installed the current version:
pnpm add quasar-extras-svg-iconsUse the equivalent bun, yarn, or npm command if your project uses a different package manager.