This guide walks you from a fresh clone of the repository to a running development server with hot-reload. You will need a backend API instance reachable over HTTP/HTTPS — see the note at the bottom for details. Total setup time is under five minutes on a standard developer machine.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/fredy-rizo/ecommerce-delivery-frontend/llms.txt
Use this file to discover all available pages before exploring further.
Install dependencies
Clone the repository (or open your existing local copy) and install all Node dependencies. Both The install resolves Vue 3, Quasar 2, Vuex 4, Vue Router 4, Axios, Socket.io-client, Firebase, and all Webpack dev-tooling declared in
npm and yarn are supported.package.json.Configure environment variables
The project loads runtime configuration from a Then populate
Firebase keys (
prod.env file in the repository root via @quasar/quasar-app-extension-dotenv. Create the file by copying the provided template:prod.env with your environment values:prod.env
| Variable | Description |
|---|---|
PORT | Port the Quasar dev server listens on. Defaults to 8080 when left blank. |
API_SERVER | Base URL of your backend REST API. Injected as baseURL for the Axios $api instance. |
PLATFROM | Deployment platform identifier (note: the key is intentionally spelled PLATFROM in the env file — do not correct the spelling or the variable will not be read). |
API_KEY, AUTH_DOMAIN, PROJECT_ID, STORAGE_BUCKET, MESSAGING_SENDER_ID, APP_ID, MEASUREMENT_ID) are also read from prod.env. See the Configuration page for the full variable reference.Start the development server
Run the Quasar dev command from the project root:Quasar compiles the application with Webpack, starts a dev server on port
8080 (or the value of PORT), and automatically opens your default browser. Hot-module replacement is active — changes to .vue and .js files are reflected instantly without a full page reload.You should see output similar to:The application requires a running backend API server. Set
API_SERVER in prod.env to the full base URL of that server (e.g. https://api.example.com) before starting the dev server. All HTTP calls made through this.$api use this value as their baseURL. Without a valid backend the login screen will appear but all authenticated requests will fail.