quasarframework/quasar · warning

Failed to open specific browser

Error message

Failed to open specific browser

What it means

openBrowser with an explicit browser option (opts) tries to open the URL in that specific browser via the `open` package (app name or binary). If that launch rejects, it warns with this message and automatically falls back to openDefault(). It indicates the requested browser could not be resolved or launched on this machine.

Source

Thrown at app-vite/lib/utils/open-browser.js:26

    open(url, {
      wait
    }).catch(err => {
      console.error(err)
      warn('Failed to open default browser')
      warn()
    })
  }

  if (opts) {
    log('Opening browser at ' + url + ' with options: ' + JSON.stringify(opts))
    log()
    open(url, {
      ...opts,
      wait
    }).catch(err => {
      console.error(err)
      warn('Failed to open specific browser')
      warn()
      openDefault()
    })
  } else {
    openDefault()
  }
}

View on GitHub (pinned to 4841521b5f)

Solutions

1. Use the exact app name the `open` package expects for your OS (e.g. 'firefox', 'google-chrome' on Linux, 'Google Chrome' on macOS, 'chrome' on Windows)
2. Verify the browser binary exists and is on PATH (`which google-chrome`)
3. Remove the specific-browser option so Quasar falls back to the default browser
4. Check the console.error output above the warning for the precise spawn failure

Example fix

// before (quasar.config.js) on Linux
devServer: { server: { open: 'Chrome' } }
// after
devServer: { server: { open: 'google-chrome' } }

// verify the specific browser binary exists before configuring it
const { execSync } = require('node:child_process')
function browserAvailable(bin) {
  try { execSync(`which ${bin}`, { stdio: 'ignore' }); return true }
  catch { return false }
}
// use only if true:
// devServer: { server: { open: 'google-chrome' } }

When it happens

Trigger: `quasar dev` with devServer.open set to a specific browser name/object (or the --browser flag) where the given app name is not a known browser alias for the OS or its binary is not installed/on PATH.

Common situations: Requesting 'chrome' when only Chromium or Edge is installed; a custom binary path with a typo or wrong platform name (e.g. 'google chrome' vs 'google-chrome' vs 'chrome' on Linux vs macOS vs Windows); browser installed in a non-standard location.

Related errors

• Failed to open default browser
• ERROR_NETWORK_PORT_NOT_AVAIL
• [Quasar] In your Vite config file, please add the Quasar plu
• The queued task for "${task.diffName}" failed
• ERROR_NETWORK_PORT_NOT_AVAIL

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