the current proxy target IP address is probably only working for a single developer at a time. this change introduces a vite.user.ts, which is ingored by GIT, and which can define a proxy_target that works for the respective developer. this does not change the default behavior, as the fallback value is still the old IP address. if the new vite.user.ts file does not exist, or if it does not export proxy_target, the fallback value is used. file vite.config.ts adds an example in a comment of how to bootstrap a vite.user.ts. |
||
|---|---|---|
| .. | ||
| .vscode | ||
| public | ||
| src | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| env.d.ts | ||
| index.html | ||
| package.json | ||
| README.md | ||
| tsconfig.config.json | ||
| tsconfig.json | ||
| vite.config.ts | ||
| yarn.lock | ||
OpenDTU web frontend
You can run the webapp locally with yarn dev. If you enter the IP of your ESP in the vite.config.ts beforehand, all api requests will even be proxied to the real ESP. Then you can develop the webapp as if it were running directly on the ESP. The yarn dev also supports hot reload, i.e. as soon as you save a vue file, it is automatically reloaded in the browser.
Project Setup
yarn install
Compile and Hot-Reload for Development
yarn dev
Type-Check, Compile and Minify for Production
yarn build
Lint with ESLint
yarn lint