Group by Tag has always been there, and every document was Untagged: tags come from the frontmatter `tags:` key, nothing but hand-typed YAML ever set one, and no generated document mentioned the key. Both templates did pass `tags: []` — `render_frontmatter` dropped every empty value on the way out, so the one place a user could have learned tags exist never printed. An empty list prints now. An empty string still does not: `owner:` teaches nothing the template already says. The chips under the title become the editor. Each carries a cross, and a `+ Tag` chip opens a field that takes a whole list — "web, prod" is two tags — and refuses one the document already carries whatever its case. It writes straight through like starring: a chip clicked off is not a draft of the document. The body owns tags, the column caches them, so the store rewrites the block and saves the body rather than patching a field the next body save would overwrite. `withFrontmatter` would have done it in one line and round-tripped everything else through the YAML dumper — `created: 2026-09-07` comes back a full timestamp, because that is what the date parsed to. So `withTags` replaces that one entry, inline or block list, and leaves the other lines byte for byte as written. `test_frontmatter_omits_empty_values` asserted the dropping this changes; it is renamed and now asserts the empty list survives. ha-relevant: yes
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Remove tseslint.configs.recommended and replace with this
tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
tseslint.configs.stylisticTypeChecked,
// Other configs...
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])
You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Enable lint rules for React
reactX.configs['recommended-typescript'],
// Enable lint rules for React DOM
reactDom.configs.recommended,
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])