Files
Sergey Savelyev 44862f65d2 Transfer Panel Details Without an Extra Layer of JSON Encoding (#14)
**Rationale:**

This made it harder to snoop on the traffic in the network monitor because it was encoded as a string.

**Changes:**

- Backend now accepts & provides the panel data as a JSON object rather than as a string
- Backend now supports compression
- Minor improvements to error handling
- Some panel structures were getting saved in the JSON when they weren't supposed to be (now this no longer happens)

Reviewed-on: #14
Co-authored-by: Sergey Savelyev <sergeysav.nn@gmail.com>
Co-committed-by: Sergey Savelyev <sergeysav.nn@gmail.com>
2026-01-03 18:24:40 -08:00
..
2024-10-20 12:37:40 -07:00
2024-10-20 12:37:40 -07:00
2024-12-04 20:00:18 -08:00
2024-10-20 12:37:40 -07:00
2024-10-20 12:37:40 -07:00
2025-01-03 00:20:56 -05:00
2025-02-14 20:39:52 -08:00
2024-10-20 12:37:40 -07:00
2024-10-20 12:37:40 -07:00
2024-10-20 12:37:40 -07:00
2024-10-20 12:37:40 -07:00
2024-12-05 20:10:31 -08:00

frontend

This template should help get you started developing with Vue 3 in Vite.

VSCode + Volar (and disable Vetur).

Type Support for .vue Imports in TS

TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need Volar to make the TypeScript language service aware of .vue types.

Customize configuration

See Vite Configuration Reference.

Project Setup

bun install

Compile and Hot-Reload for Development

bun dev

Type-Check, Compile and Minify for Production

bun build

Lint with ESLint

bun lint