ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #quasar
Guide to decide between Quasar fibers and thread‑per‑request for Java web apps, with a comparison table, trade‑offs, and a step‑by‑step Spring Boot integration example.
Learn how Quasar’s built‑in TypeScript extension catches errors early, shows them in dev and build, and what trade‑offs to consider.
Quasar fibers enable many logical tasks on few carrier threads via load-time bytecode instrumentation. This note covers minimal setup, shared-memory boundaries, and operational checks.
quasarbytecode-instrumentationTasadduq Burneyowner26.5K rep · 26 Dec 2025, 10:52 UTCLearn how to configure Quasar’s QTable for server‑side pagination and sorting, with loading indicators, error handling, and state persistence. Step‑by‑step guide with example code and validation tips.
Quasar CLI’s quasar upgrade command updates @quasar/app and related packages to the latest stable release using the project’s package manager. The command does not create any backup of package.json , lockfiles or source code before modifying dependencies. As a result, recovering from a failed upgrade depends on manually reinstalling the previous version reco
Our production app runs on Quasar v1 with Vue 2, and since v1 is in maintenance status we need to move to Quasar v2, which is built on Vue 3. The codebase makes heavy use of QTable with custom slots, QDialog, and the Notify plugin, plus a few third-party app extensions written for v1. The constraint is that Quasar v2 is not a drop-in upgrade: the CLI split i
Integration Mode Trade-offs When architecting a Quasar application that requires both high search-engine visibility and offline capabilities, the choice between Server-Side Rendering (SSR) and Progressive Web App (PWA) modes presents a conflict in build configuration. SSR improves the time-to-first-paint and SEO by rendering pages on the server, while PWA mo