Frontend Code

The frontends are Vue 3 applications built with Vite and tested with Vitest. The aim is TypeScript for code that runs in the browser. The editor, lawmaking, the demo and frontend-shared use the setup on this page; the PoC frontends are still JavaScript and will be migrated later. Three kinds of file stay JavaScript in any case: scripts that run in plain Node, the modules those scripts load, and generated files such as grammar.generated.js and nldd-components.js. In the demo, the first two are the modules in src/i18n/ (the dictionaries, the language table and hash.js) and src/data/materialize.js, which the scripts in scripts/ and corpus/demo/tools/ load.

The tsconfigs

An app follows the layout that create-vue generates for a TypeScript project. tsconfig.json references three programs, one per environment:

npm run typecheck runs vue-tsc --build over all three, and CI runs it as a separate step in the frontend job. The app config sets noUncheckedIndexedAccess, so an arr[i] lookup is typed as possibly undefined, and allowJs where JavaScript modules remain. vitest.config.ts builds on vite.config.ts, so a test that imports a component gets the same template compiler options as the app. A test that mounts a component runs in happy-dom.

Conventions

• Nothing is compiled ahead of time. Vite and Vitest strip the types when they bundle or test the source.
• An import of a TypeScript module leaves out the extension ('./values'). Vite and Vitest resolve it, and the code only runs through them. Plain Node does not resolve an import without an extension, so a module that a node script loads keeps its .js imports.
• The check runs vue-tsc, not tsc, because only vue-tsc reads the script blocks in .vue files. The workspace pins TypeScript 6 through an overrides entry in the root package.json: vue-tsc builds on the JavaScript compiler API that TypeScript 7 no longer ships. The docs site has its own lockfile and stays on TypeScript 7.