Adds eslint-plugin-boundaries with one element type per Tier-1 domain and an explicit allow-list encoding the architectural dependency graph: - document may import from: shared, person, tag, ocr, activity, conversation - geschichte may import from: shared, person, document - ocr may import from: shared, document - activity may import from: shared, notification - all others (person, tag, user, notification, conversation): shared only - routes may import from any domain Default is 'disallow', so any unlisted cross-domain import is an error. Two eslint-disable-next-line comments remain in shared/discussion where person-domain helpers (getInitials, formatLifeDateRange) are needed to render participant metadata; moving them to shared would lose the person-type context. Closes #410 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sv
Everything you need to build a Svelte project, powered by sv.
Creating a project
If you're seeing this, you've probably already done this step. Congrats!
# create a new project in the current directory
npx sv create
# create a new project in my-app
npx sv create my-app
Developing
Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:
npm run dev
# or start the server and open the app in a new browser tab
npm run dev -- --open
Building
To create a production version of your app:
npm run build
You can preview the production build with npm run preview.
To deploy your app, you may need to install an adapter for your target environment.