No Quasar project folder detected. Using the current folder

Error message

No Quasar project folder detected. Using the current folder as the target.

What it means

getAppInfo in icongenie walks up from the current directory looking for a Quasar project folder (quasar.config file). When none is found, it does not hard-fail because Quasar may be used as a library in custom Vite/Electron setups; instead it warns and falls back to process.cwd() as the target folder. Asset generation only happens for mode folders that actually exist under that target.

Source

Thrown at icongenie/lib/utils/app-paths.js:27

  while (appDir.length !== 0 && appDir.at(-1) !== sep) {
    if (
      existsSync(join(appDir, 'quasar.config.js')) ||
      existsSync(join(appDir, 'quasar.config.mjs')) ||
      existsSync(join(appDir, 'quasar.config.ts')) ||
      existsSync(join(appDir, 'quasar.config.cjs')) ||
      existsSync(join(appDir, 'quasar.conf.js')) // legacy
    ) {
      return appDir
    }

    appDir = normalize(join(appDir, '..'))
  }

  // no Quasar CLI project detected; Quasar might still be used as a
  // library (custom Vite/Electron setups), so target the current folder
  // instead of hard-failing -- only modes whose target folders actually
  // exist under it will get assets generated
  warn(
    'No Quasar project folder detected. Using the current folder as the target.'
  )
  return process.cwd()
}

export const appDir = getAppInfo()
export const resolveDir = dir => join(appDir, dir)

View on GitHub (pinned to 4841521b5f)

Solutions

cd into the root of your Quasar CLI project (the folder containing quasar.config.js or its parent chain) before running icongenie
Use the -t/--target flag or profile 'target' setting to explicitly point icongenie at your Quasar project folder
If Quasar is used as a library, accept the warning and ensure the mode folders (src-pwa, src-cordova, etc.) exist under the current folder

Example fix

// before (run in ~ not in project)
cd ~ && npx icongenie generate
// after
cd ~/my-quasar-app && npx icongenie generate

Defensive patterns

Strategy: validation

Validate before calling

import { existsSync } from 'node:fs'
import { resolve } from 'node:path'
const root = resolve('quasar.config.js')
if (!existsSync(root)) {
  console.error('Run icongenie from a Quasar project folder (quasar.config.js not found)')
  process.exit(1)
}

Type guard

const isQuasarProject = (dir) => existsSync(join(dir, 'quasar.config.js')) || existsSync(join(dir, 'quasar.config.ts'))

Prevention

Always run icongenie from the Quasar project root
Add a sanity check in CI scripts verifying quasar.config.js exists before invoking icongenie
Use the target/profile option to pin the project folder explicitly

When it happens

Trigger: Running any icongenie command (e.g. `icongenie generate`) from a directory that is not inside a Quasar CLI project — no quasar.config.js found in cwd or any parent.

Common situations: Running icongenie in a plain Node/Vite repo, running it from the wrong subfolder or home directory, or a renamed/moved project where the quasar.config file is no longer an ancestor of cwd.

Related errors

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