quasarframework/quasar · info

BEX support detected already. Aborting.

Error message

BEX support detected already. Aborting.

What it means

addMode checks isModeInstalled(appPaths, 'bex') before installing BEX mode. If a src-bex directory (the mode's marker) already exists, the install is aborted; unless silent:true, it warns 'BEX support detected already. Aborting.' and only ensures the mode's package.json/deps are in place.

Source

Thrown at app-vite/lib/modes/bex/bex-installation.js:25

  ensureModePackageJsonAndWorkspace,
  isModeInstalled
} from '../modes-utils.js'

/**
 * @param {{
 *   ctx: import('../../../types/configuration/context').InternalQuasarContext,
 *   silent: boolean
 * }} options
 */
export async function addMode({ ctx, silent }) {
  const { appPaths, cacheProxy } = ctx

  if (isModeInstalled(appPaths, 'bex')) {
    const forceInstall = await ensureModePackageJsonAndWorkspace('bex', ctx)
    await ensureModeDeps('bex', ctx, forceInstall)

    if (silent !== true) {
      warn('BEX support detected already. Aborting.')
    }

    return
  }

  const promptSession = await createPromptSession('Installing BEX Mode...')

  const copyTask = promptSession.taskLog({ title: 'Creating /src-bex...' })

  await copyModeWorkspace('bex', ctx)
  fse.copySync(appPaths.resolve.cli('templates/bex/common'), appPaths.bexDir)

  const hasTypescript = await cacheProxy.getModule('hasTypescript')
  const format = hasTypescript ? 'ts' : 'js'
  fse.copySync(appPaths.resolve.cli(`templates/bex/${format}`), appPaths.bexDir)

  copyTask.success('Created /src-bex')
  await ensureModeDeps('bex', ctx, true)

View on GitHub (pinned to 4841521b5f)

Solutions

1. Nothing to fix: BEX mode is already installed; remove `quasar mode add bex` from the script or guard it.
2. If you intentionally want a fresh scaffold, delete the src-bex directory (back up custom code first) and re-run `quasar mode add bex`.
3. Pass silent:true when invoking addMode programmatically to suppress the warning.

Example fix

// before (CI script)
quasar mode add bex
quasar build -m bex
// after
[ -d src-bex ] || quasar mode add bex
quasar build -m bex

const fs = require('fs')
if (!fs.existsSync('src-bex')) {
  require('child_process').execSync('npx quasar mode add bex', { stdio: 'inherit' })
}

When it happens

Trigger: Running `quasar mode add bex` (or an install flow calling addMode) when src-bex/ is already present in the project; silent !== true makes the warning visible.

Common situations: Re-running the add command after a previous successful install; CI script that unconditionally runs `quasar mode add bex`; manual creation of src-bex folder.

Related errors

• Failed to reconnect to the background script.
• Failed to inform "${portName}" about the port list.
• Failed to query the tabs to revive the content script connec
• Error while triggering listener${plural} for event: "${messa
• Failed to forward message of type "${packet.type}" from "${p

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