chore(deps-dev): bump @quasar/app-vite from 2.6.2 to 3.0.1 in /frontend

[dependabot]

Bumps @quasar/app-vite from 2.6.2 to 3.0.1.

Release notes

Sourced from @​quasar/app-vite's releases.

@​quasar/app-vite-v3.0.1

Changes

• fix(app-vite): Capacitor & Cordova modes -> www folder not cleaned before build #18351

Donations

Quasar Framework is an open-source MIT-licensed project made possible due to the generous contributions by sponsors and backers. If you are interested in supporting this project, please consider the following:

• Becoming a sponsor on Github
• One-off donation via PayPal

@​quasar/app-vite-v3.0.0

Bird's eye view on what's new

• ⚡ Blazing Fast Compilation: We've replaced esbuild with Rolldown for /src-* folders and completely redesigned the build architecture. Build steps are now parallelized across all Quasar modes, resulting in significantly faster speeds and a smaller footprint for your production distributables.

• ⚙️ Next-Gen Environment Management: We’ve redesigned env file management from the ground up. You will no longer need to restart the dev server when making changes to these files, and you can now use them directly within your quasar.config file too!

• 🔒 Enhanced Security & Modern Standards: We’ve migrated from process.env to the modern import.meta.env (aligning with Vite's native model) with full TypeScript support. A new security layer ensures client-side files only use a configurable prefix for env definitions, preventing potential leaks of sensitive data.

• 📦 Smarter Dependency Isolation: We now have a clear separation of dependencies for each Quasar mode. You can install mode-specific packages directly in their respective /src-* folders. For example, the default Electron app will no longer require dependencies to be installed in its dist folder—only what you explicitly install in /src-electron will be included.

• 🌍 Redesigned SSR Architecture: SSR mode now features superior support for custom web servers and proper TypeScript integration. When adding SSR, the CLI will prompt you to spawn a preconfigured /src-ssr folder using Hono, Fastify, Express, or Koa (let us know what other out-of-the-box servers you’d like!).

• 📂 New Server Assets Folder for SSR: We've introduced a /src-ssr/server-assets folder alongside helpful utility functions. This makes it incredibly easy to reference assets (like HTTPS certificates) across dev and production runtimes, eliminating the strict need for an Apache/Nginx wrapper. We've also made the serverless support a breeze.

• 🚀 Paving the Way for SSG: This new SSR architecture lays the necessary groundwork for us to finally release Static Site Generation (SSG) mode in the future.

• 🖥️ Revamped Electron Mode: We’ve added lots of new features to make desktop development smoother. Similar to SSR, we've introduced a /src-electron/electron-assets folder. Referencing files from here (or from the /public folder) is now much easier via new utility methods available in both /src-electron and /src.

• 🛣️ Vue Router: First-class support for the filename-based routing.

• 🚀 Smarter reloads (when absolutely needed): You'll notice the DX on dev has improved significantly, with even smarter heuristics when changing the quasar.config file or the dotenv files.

• 🛠️ Modernized Core: The codebase has been updated to take full advantage of Node.js v22+ features, alongside countless other small but significant improvements across all Quasar modes to boost your productivity. The CLI uses significantly less dependencies.

• ...and sooo many other new features and enhancements!

Upgrade Guide

Please refer to docs for the Upgrade Guide. Read top to bottom first.

Donations

Quasar Framework is an open-source MIT-licensed project made possible due to the generous contributions by sponsors and backers. If you are interested in supporting this project, please consider the following:

• Becoming a sponsor on Github
• One-off donation via PayPal

@​quasar/app-vite-v3.0.0-rc.6

Changes

• fix(app-vite): Electron on Windows host -> quirk on dev mode hindering execution

... (truncated)

Commits

• 5faf39f chore(app-vite): Bump version
• 73708b0 fix(app-vite): Capacitor & Cordova modes -> www folder not cleaned before bui...
• 97804d7 fix(docs): highlight on the buggy safari regex engine
• 4e917d2 chore(ui/testing): remove console.log statement
• 26d0b1f chore(create-quasar): Bump version
• 1c41a9a fix(create-quasar): correct title/label mismatch in JS app-vite template (fix...
• 657205c chore(create-quasar): Bump version
• a0db496 chore(app-vite): Bump version
• ad02993 chore(ui): Bump version
• 230b171 fix+perf(QDialog): css instead of js approach to fix page scroll loss functio...
• Additional commits viewable in compare view

[greptile-apps]

Greptile Summary

This PR updates the Quasar Vite app tooling in the frontend.

• Bumps @quasar/app-vite to ^3.0.1 in frontend/package.json.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
frontend/package.json	Updates the frontend Quasar Vite app package version.

_{Reviews (2): Last reviewed commit: "chore(deps-dev): bump @quasar/app-vite f..." | Re-trigger Greptile}

[greptile-apps]

Legacy Env Reads Become Undefined

When the v3 Quasar CLI builds this app, the existing frontend/src/environment.ts still reads process.env.VUE_APP_PRODUCTION and process.env.DEV. The upgraded CLI now uses the Vite-style env path, so those legacy values can be missing and asBoolean(undefined) will throw during app startup or build initialization.

Prompt To Fix With AI

This is a comment left during a code review.
Path: frontend/package.json
Line: 51

Comment:
**Legacy Env Reads Become Undefined**

When the v3 Quasar CLI builds this app, the existing `frontend/src/environment.ts` still reads `process.env.VUE_APP_PRODUCTION` and `process.env.DEV`. The upgraded CLI now uses the Vite-style env path, so those legacy values can be missing and `asBoolean(undefined)` will throw during app startup or build initialization.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Backend URL Prefix Can Disappear

This upgrade changes the client env exposure model while the app still depends on import.meta.env.BACKEND_URL, which is only exposed through a custom non-VITE_ prefix in frontend/quasar.config.ts. If the v3 config path no longer applies that custom prefix the same way, BACKEND_URL is omitted and asString(undefined) crashes the frontend before it can start.

Prompt To Fix With AI

This is a comment left during a code review.
Path: frontend/package.json
Line: 51

Comment:
**Backend URL Prefix Can Disappear**

This upgrade changes the client env exposure model while the app still depends on `import.meta.env.BACKEND_URL`, which is only exposed through a custom non-`VITE_` prefix in `frontend/quasar.config.ts`. If the v3 config path no longer applies that custom prefix the same way, `BACKEND_URL` is omitted and `asString(undefined)` crashes the frontend before it can start.

How can I resolve this? If you propose a fix, please make it concise.