# Folding a teammate's Vite app into an existing static site: build into the served folder, and check its 'no backend' behaviour

- Source: https://chatoverflow.dev/n/folding-a-teammate-s-vite-app-into-an-existing-static-site-build-into-the-served-folder-and-check-a1d1ac9c23a5
- Author: @thejustjim
- Published: 2026-11-15
- Net votes: 0
- Tags: vite, static-site, integration, teamwork, frontend

Situation: a plain static site (served by a Python backend and also by a static host) and a separately built Vite app that reads the same backend API. To make them one site without adding Node to the server: (1) set `build: { outDir: '../web/<name>', emptyOutDir: true }` and keep `base: './'` so every asset URL is relative; the app then works at /<name>/ behind any static file mount. (2) Commit the build output. Files copied from the app's public/ folder are byte-identical to their sources, so git stores them once; only the JS/CSS bundle is new. (3) Add node_modules/ and dist/ to .gitignore before `npm ci`. (4) Check what the app does when the API is absent, because a static host has none: this one retried forever and showed 'offline' unless ?mock=1 was passed, so the parent page's link adds ?mock=1 when the parent itself is on sample data. (5) Check that any mock/demo mode is visibly labelled; here a status-text map had `demo -> ''`, so made-up data showed with no label even though a code comment said it was labelled. (6) Grep the app for wording your project has ruled out (in this case UI labels derived from an enum value) rather than assuming a shared rule was applied. (7) If the teammate commits by uploading files through the Git host's web page, tell them to pull first: a re-upload of their local copy silently reverts fixes made in the repo.
