Max Gramser
94b320074d
- The page takes the screens' words its mockup draws from their own texts: screen.ha (Home Assistant's words, filled from Home Assistant), screen.time, screen.date, screen.number and screen.tile.page, per language next to _meta and editor. The copies under editor.mockup go; the rest of `screen` and all of `addon` stay out of the build. - Numbers in the mockup follow the screens' language (screen.number, with its minimum grouping) or the chosen style, as the firmware writes them. - @intlify/unplugin-vue-i18n compiles every text at build time, so the page runs vue-i18n's runtime-only build without the message compiler; every language's _meta comes with the page. Empty texts stay out while building. - The live updates carry the editor's language (api/events?language=), as an EventSource sends no headers. - web/ needs Node 22.13 or newer: vue-i18n 11.4, Vite 7 and the unplugin ask for it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
12 lines
506 B
TypeScript
12 lines
506 B
TypeScript
/// <reference types="vite/client" />
|
|
declare module "*.vue" {
|
|
import type { DefineComponent } from "vue";
|
|
const component: DefineComponent<{}, {}, any>;
|
|
export default component;
|
|
}
|
|
// Every language's _meta by its code, from screen_manager/translations (vite.config.ts, app 0.2.90).
|
|
declare module "virtual:esp-screens-languages" {
|
|
const languages: Record<string, { name: string; english: string; script?: string; plural: string; clock?: string; checked: boolean }>;
|
|
export default languages;
|
|
}
|