Upgrade to Quasar v2.19 / app-vite 2.5.4 breaks QIcon with 'material-icons-outlined'

[tofi86]

What happened?

Upgrade to Quasar v2.19 / app-vite 2.5.4 with quasar upgrade -i breaks QIcon's prefixed with o_ when using 'material-icons-outlined'.

The page doesn't render at all.

What did you expect to happen?

The page still shows fine.

Reproduction URL

https://stackblitz.com/edit/quasarframework-stackblitz-templates-7xltmdzg?file=quasar.config.js,package.json,src%2Fpages%2FIndexPage.vue&title=Quasar%20Framework%20-%20app-vite%20v2

How to reproduce?

1. Go to the provided reproduction link
2. See that the whole page isn't loading
3. Go to https://stackblitz.com/edit/quasarframework-stackblitz-templates-kxu6xlai?file=quasar.config.js,package.json,src%2Fpages%2FIndexPage.vue&title=Quasar%20Framework%202.18.7%20-%20app-vite%20v2.5.2 which uses Quasar 2.18.7 and app-vite 2.5.2 and see that it worked before with just changing these two dependencies.

Flavour

Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)

Areas

Quasar Extras (@quasar/extras)

Platforms/Browsers

No response

Quasar info output

Operating System - Darwin(24.6.0) - darwin/arm64
NodeJs - 22.22.2

Global packages
  NPM - 10.9.7
  yarn - Not installed
  pnpm - Not installed
  bun - 1.3.10
  @quasar/cli - 3.0.0
  @quasar/icongenie - Not installed
  cordova - Not installed

Important local packages
  quasar - 2.19.1 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
  @quasar/app-vite - 2.5.4 -- Quasar Framework App CLI with Vite
  @quasar/extras - 1.17.0 -- Quasar Framework fonts, icons and animations
  eslint-plugin-quasar - Not installed
  vue - 3.5.30 -- The progressive JavaScript framework for building modern web UI.
  vue-router - 5.0.4
  pinia - 3.0.4 -- Intuitive, type safe and flexible Store for Vue
  vite - 7.3.1 -- Native-ESM powered web dev build tool
  vite-plugin-checker - Not installed
  eslint - 9.39.4 -- An AST-based pattern checker for JavaScript.
  esbuild - 0.25.12 -- An extremely fast JavaScript and CSS bundler and minifier.
  typescript - 5.9.3 -- TypeScript is a language for application scale JavaScript development
  workbox-build - Not installed
  register-service-worker - Not installed
  electron - Not installed
  @electron/packager - Not installed
  electron-builder - Not installed
  @capacitor/core - Not installed
  @capacitor/cli - Not installed
  @capacitor/android - Not installed
  @capacitor/ios - Not installed

Quasar App Extensions
  *None installed*

Networking
  Host - MacBook-Pro-von-Tobias-2.local
  en0 - 10.3.2.30
  utun4 - 10.8.15.7
  en12 - 10.18.2.3

Relevant log output

TypeError: can't access property 1, matches is null
    type quasar.client.js:1519
    refreshComputed reactivity.esm-bundler.js:393
    get value reactivity.esm-bundler.js:1724
    setup quasar.client.js:1534
    renderComponentRoot runtime-core.esm-bundler.js:4550
    componentUpdateFn runtime-core.esm-bundler.js:6099
    run reactivity.esm-bundler.js:239

Additional context

No response

[Tenrys]

I ran into this too, had opencode/Claude fix it for me in a patch for now.

% WebFetch https://github.com/quasarframework/quasar/blame/dev/ui/src/components/icon/QIcon.js

The blame is very clear. Line 172 was last touched by the commit on Mar 23, 2026: feat(ui): apply new linting rules. That refactor introduced the bug — before that commit, the code was structured differently (the symMatches pattern using a local variable was added in the May 2022 commit, and the matMatches branch had worked for years). The linting refactor on March 23rd shuffled the else if chain and introduced const matMatches = icon.match(matRE) as a local variable — but accidentally left matches[1] instead of matMatches[1] on line 172. It's a very fresh regression, just 2 days old.

[damvaz]

@rstoenescu we need this fix please, thanks! 🫰

[rstoenescu]

Fixed it in Quasar v2.19.2 (and just released it)