ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #quasar
Quasar's --ssr flag generates a Node server that pre-renders Vue components to HTML, improving first paint and SEO—but it trades static hosting for a runtime dependency.
An architecture note on Quasar's PWA extension: where Workbox-generated service workers help, where trust boundaries sit, and which operational checks catch stale caches and API failures.
Learn how to use Quasar boot files to centralize app initialization, manage plugin registration order, and avoid common SSR pitfalls when setting up Vue applications.
When datasets grow, a Quasar QTable that renders every row in the browser becomes sluggish. This post shows how to use QTable’s request event to delegate slicing, sorting, and total counts to a backend API, keeping the client lean and responsive.
If your Quasar application visibly jumps after page load, the cause is usually a mismatch between server-rendered HTML and client-side layout recalculation. Learn to diagnose and fix q-page layout shifts using the view prop, skeleton loaders, and DevTools.
Quasar’s CLI lets you build SPA, PWA, SSR, and native apps from one codebase. Learn how to add modes, switch rendering strategies, and verify artifacts—all while understanding the trade‑offs.
Quasar compiles one Vue 3 codebase into SPA, PWA, SSR, Electron, Capacitor, and browser extension builds. Here's how the platform isolation model works and where it breaks.
Learn how to architect Quasar SSR to improve SEO and performance, including strategies for data boundaries, hydration verification, and avoiding common server-side memory leaks.
Quasar's multi-mode build system lets one Vue codebase ship as SPA, PWA, SSR, mobile, and Electron desktop apps. Here's how modes work, how to gate platform-specific code, and why each added mode is a maintenance commitment.
electron