Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/fredy-rizo/despacho-frontend/llms.txt

Use this file to discover all available pages before exploring further.

Getting the Lex Consultoría Despacho Frontend running on your local machine takes fewer than five minutes. The project uses the Quasar CLI as its primary development and build tool, layered on top of Vite for lightning-fast module resolution. Follow the steps below from a fresh checkout to a live hot-reloading dev server, and then on to a production-ready distribution bundle.

Prerequisites

Before you begin, confirm that the following tools are available in your environment.

Node.js ≥ 18

Any active LTS release from Node 18 through Node 28 is supported, as declared in package.json engines.

npm ≥ 6.13.4 or Yarn ≥ 1.21.1

Either package manager works. Use whichever your team standardizes on — all commands below show both variants.

Quasar CLI v2

The @quasar/cli global binary drives quasar dev, quasar build, and quasar prepare. Install it once per machine.
Do not mix package managers in the same project. If you initialize with yarn, commit the yarn.lock file and use yarn for all subsequent installs. Using npm install in a Yarn-managed project will generate a conflicting package-lock.json.

Installation Steps

1
Clone the repository
2
Obtain a local copy of the source code from version control. Replace the URL below with your team’s actual remote if it differs.
3
git clone https://github.com/fredy-rizo/despacho-frontend.git
cd despacho-frontend
4
Install project dependencies
5
Install all runtime and development dependencies declared in package.json. A postinstall hook automatically runs quasar prepare to generate the type-helper shims after installation completes.
6
npm
npm install
yarn
yarn
7
Install the Quasar CLI globally
8
The quasar binary must be available on your PATH. Install it globally once — it is shared across all Quasar projects on the machine and does not need to be re-installed per project.
9
npm install -g @quasar/cli
10
Verify the installation:
11
quasar --version
12
Start the development server
13
Launch the app in development mode. Quasar’s dev server wraps Vite, providing hot-module replacement, Vue DevTools integration, and detailed error overlays. The open: true setting in quasar.config.js causes your default browser to open automatically once the server is ready.
14
quasar dev
15
The application will be available at http://localhost:9000 (Quasar’s default port) and the browser tab opens on its own. Edit any file under src/ and the page updates instantly without a full reload.
16
The SPA expects the backend REST API to be accessible at http://localhost:2101. Start the backend service before making any authenticated requests or the Axios calls will fail with a network error.
17
Build for production
18
Compile and bundle the application for deployment. Quasar invokes Vite’s production build, applies tree-shaking, and outputs the hashed static assets to the dist/spa/ directory.
19
quasar build
20
The resulting dist/spa/ folder can be served from any static hosting service or CDN. Because the router runs in hash mode, no server-side URL rewrite rules are required.

Additional Commands

Lint

Run ESLint across all JavaScript and Vue files using the flat config defined in eslint.config.js. Fix issues before committing to keep the codebase consistent.
npm run lint

Format

Auto-format all source files with Prettier. The .prettierrc.json file at the project root defines the formatting rules applied to JS, Vue, SCSS, HTML, Markdown, and JSON files.
npm run format
Add npm run lint && npm run format (or the yarn equivalents) as a pre-commit hook using a tool like Husky to enforce code quality automatically on every commit.

Environment Summary

ToolMinimum VersionPurpose
Node.js18JavaScript runtime
npm6.13.4Package manager (alternative)
Yarn1.21.1Package manager (alternative)
@quasar/cli2.xDev server, build, prepare
Backend APIhttp://localhost:2101

Build docs developers (and LLMs) love