What causes "No source icon file specified, so using the sample one" in quasarframework/quasar?

Pass your source icon explicitly: icongenie g --icon path/to/icon.png

No source icon file specified, so using the sample one

Error message

No source icon file specified, so using the sample one

What it means

The icon() argv parser in icongenie checks for a source icon path; when none is given, it warns and falls back to the bundled sample icon (samples/icongenie-icon.png). Generation still proceeds, but output icons are based on Quasar's placeholder image, not your icon.

Source

Thrown at icongenie/lib/utils/parse-argv.js:139

  if (isAbsolute(__path)) {
    return existsSync(__path) ? __path : null
  }

  let localIcon = resolve(process.cwd(), __path)

  if (existsSync(localIcon)) {
    return localIcon
  }

  localIcon = resolve(appDir, __path)

  return existsSync(localIcon) ? localIcon : null
}

function icon(value, argv) {
  if (!value) {
    warn(`No source icon file specified, so using the sample one`)
    argv.icon = normalize(
      join(import.meta.dirname, '../../samples/icongenie-icon.png')
    )
    return
  }

  argv.icon = parseIconPath(value)

  if (!argv.icon) {
    die(`Path to source icon file does not exists: "${value}"`)
  }

  const { width, height } = getPngSize(argv.icon)

  if (width === 0 && height === 0) {
    die(`Icon source is not a PNG file!`)
  }

View on GitHub (pinned to 4841521b5f)

Solutions

Pass your source icon explicitly: icongenie g --icon path/to/icon.png
Set the icon field in your icongenie-*.json profile
If the sample icon was unintended, delete the generated assets and regenerate after adding --icon

Example fix

// before
icongenie g --mode all
// after
icongenie g --mode all --icon src/assets/logo-1024x1024.png

Defensive patterns

Strategy: validation

Validate before calling

import { existsSync } from 'node:fs'
const iconPath = argv.icon || profile.icon
if (!iconPath || !existsSync(iconPath)) {
  throw new Error('Source icon missing: pass -i/--icon or set icon in the profile')
}

Type guard

const hasIcon = (opts) => typeof opts?.icon === 'string' && opts.icon.length > 0 && existsSync(opts.icon)

Prevention

Always pass --icon with an absolute or project-relative path
Declare icon in your icongenie profile so it is versioned
Check the generated icons visually once to catch accidental sample-icon use

When it happens

Trigger: Running `icongenie generate` (or `quasar icongenie g`) without -i/--icon and without an 'icon' entry in the profile, in a folder lacking any detectable default icon.

Common situations: Forgetting the -i flag on first run, a mistyped icon path treated as falsy, or scripted CI calls that omit the icon parameter.

Related errors

AI-assisted analysis of quasarframework/quasar@4841521b5f (2026-08-30). Data as JSON: /api/errors/82236ab7a9f2a769. Report an issue: GitHub.