quasarframework/quasar · warning
The file defined in quasar.config > bex > extraScripts > "${
Error message
The file defined in quasar.config > bex > extraScripts > "${rawName}" does NOT exist. Skipping. What it means
extractBexScripts also processes quasar.config > bex > extraScripts. Each raw name is resolved against the src-bex directory; when the file does not exist the warning is emitted and the script is skipped instead of being compiled into the BEX.
Source
Thrown at app-vite/lib/modes/bex/bex-utils.js:181
)
warn()
return
}
const entry = getCompilationEntry(quasarConf, inputFile, scriptName)
if (!scriptNameSet.has(entry.name)) {
scriptNameSet.add(entry.name)
scriptList.push(entry)
}
})
})
quasarConf.bex.extraScripts.forEach(rawName => {
const inputFile = quasarConf.ctx.appPaths.resolve.bex(rawName)
if (!fse.existsSync(inputFile)) {
warn()
warn(
`The file defined in quasar.config > bex > extraScripts > "${rawName}" does NOT exist. Skipping.`
)
warn()
return
}
const scriptName = rawName.replace(scriptExtRE, '')
const entry = getCompilationEntry(quasarConf, inputFile, scriptName)
if (!scriptNameSet.has(entry.name)) {
scriptNameSet.add(entry.name)
scriptList.push(entry)
}
})
return scriptList
}
export function copyBexAssets(quasarConf, clean = false) {View on GitHub (pinned to 4841521b5f)
Solutions
- Move the script file into src-bex (extraScripts paths resolve relative to src-bex).
- Fix the path/name in quasar.config > bex > extraScripts.
- Remove the stale entry if the script is no longer needed.
- Restart the dev server / rebuild after changing quasar.config so it is reloaded.
Example fix
// before (quasar.config.js)
bex: { extraScripts: ['extras/my-script.js'] } // file is at ./extras/my-script.js
// after
bex: { extraScripts: ['my-script.js'] } // moved to src-bex/my-script.js Defensive patterns
Strategy: validation
Validate before calling
const fs = require('fs'), path = require('path')
for (const s of require('./quasar.config.js').bex?.extraScripts || []) {
if (!fs.existsSync(path.join('src-bex', s))) throw new Error(`extraScripts entry missing (paths are relative to src-bex): ${s}`)
} Prevention
- Remember extraScripts resolve relative to src-bex, not the project root.
- Keep extraScripts entries minimal and documented in quasar.config comments.
- Restart dev/build after editing quasar.config so changes take effect.
When it happens
Trigger: quasar.config > bex > extraScripts array contains an entry whose file cannot be found via appPaths.resolve.bex(rawName) (i.e. not inside src-bex).
Common situations: Config written expecting paths relative to project root instead of src-bex; script file deleted or renamed; typos in the config entry; forgetting that extraScripts must live within src-bex.
Related errors
- The file defined in bex manifest > background > service_work
- The file defined in bex manifest > background > scripts > "$
- The file defined in bex manifest > content_scripts > js > "$
- [Quasar] In your Vite config file, please add the Quasar plu
- Failed to reconnect to the background script.
AI-assisted analysis of quasarframework/quasar@4841521b5f (2026-08-30).
Data as JSON: /api/errors/2bbbc21e8ac5750d.
Report an issue: GitHub.