quasarframework/quasar · warning
No ${mode.toUpperCase()} support detected. Aborting.
Error message
No ${mode.toUpperCase()} support detected. Aborting. What it means
`quasar mode remove <MODE>` checks whether the mode's support folder (e.g. /src-pwa, /src-electron) exists before deleting anything. If the mode was never added (or was already removed), the CLI warns and aborts instead of deleting blindly. Exit code 0 — no harm was done.
Source
Thrown at app-vite/lib/cmd/mode.js:147
!ssrWebservers.some(entry => entry.value === argv.webserver)
) {
fatal(
`Unknown SSR webserver "${argv.webserver}". Valid values: ${ssrWebservers.map(entry => entry.value).join(' | ')}`
)
}
if (action === 'add') {
const { addMode } = await import(`../modes/${mode}/${mode}-installation.js`)
await addMode({
ctx,
webserver: argv.webserver,
filenameBasedRouting: argv['filename-based-routing'],
appId: argv['app-id'],
appName: argv['app-name']
})
} else if (action === 'remove') {
if (!isModeInstalled(ctx.appPaths, mode)) {
warn(`No ${mode.toUpperCase()} support detected. Aborting.`)
return
}
const promptSession = await createPromptSession(
`Removing ${mode.toUpperCase()} Mode...`
)
if (argv.yes !== true) {
const { go } = await promptSession.prompt({
go: () =>
promptSession.confirm({
message: `Will remove /src-${mode} folder. Are you sure?`,
initialValue: false
})
})
if (!go) {
promptSession.cancel('Aborted by user')
process.exit(1)View on GitHub (pinned to 4841521b5f)
Solutions
- Do nothing — the mode is not installed, which is the desired end state.
- Verify installed modes with `quasar mode` before scripting removal.
- If the mode should be installed, run `quasar mode add <mode>` first.
Example fix
// before ci-clean.sh: quasar mode remove pwa || true // after ci-clean.sh: quasar mode | grep -q 'Mode PWA.*yes' && quasar mode remove pwa --yes
Defensive patterns
Strategy: validation
Validate before calling
// bash: only remove when installed
quasar mode | grep -q "Mode ${MODE^^}.*yes" && quasar mode remove "$MODE" --yes Try / catch
// the warning is not fatal (exit 0); treat absence as success in scripts
if (!output.includes('Aborting')) { /* proceed */ } Prevention
- Check `quasar mode` output before remove operations.
- Make idempotent cleanup scripts tolerant of already-removed modes.
- Pass --yes in CI to avoid interactive prompts on real removals.
When it happens
Trigger: Running `quasar mode remove <mode>` when `isModeInstalled(ctx.appPaths, mode)` returns false, i.e. the mode's src directory is missing from the project (mode.js:145-148).
Common situations: Cleanup scripts that remove all modes unconditionally; running remove twice; typos in a CI script where the mode was never actually added to this project; a fresh clone that lacks the mode folder.
Related errors
- No such App Extension is installed
- ERR_PARSE_ARGS_UNKNOWN_OPTION
- ERR_PARSE_ARGS_UNKNOWN_OPTION
- ERR_PARSE_ARGS_UNKNOWN_OPTION
- Wrong number of parameters (${argv._.length}).
AI-assisted analysis of quasarframework/quasar@4841521b5f (2026-08-30).
Data as JSON: /api/errors/0ccbda3db7eb3ebd.
Report an issue: GitHub.