Migration Guide (legacy -> Svelte.js)

This guide lists the known legacy or non-compliant app folders and the concrete migration tasks required to align with project rules (Svelte.js only, no SvelteKit, no TypeScript, no React). It is based on files currently in the repo.

Global migration rules

• Target stack: Svelte.js with Vite (no SvelteKit, no TypeScript, no React).
• Svelte views are presentational only; move logic/validation to backend.
• Use DB-only translations (no local translation folders in active code).
• Ensure backend access checks gate app usage.
• Document each migration step in AblaufProtokoll.md.

Per-folder migration checklist

apps/auction

Detected:

• Root uses React/Vite (App.jsx, main.jsx, package.json with React).
• Separate backend under apps/auction/backend.
• A Svelte frontend exists at apps/auction/frontend.

Tasks:

• Decide the target frontend (prefer Svelte in apps/auction/frontend).
• Remove React/Vite root app or migrate its UI to Svelte.
• Align API usage with central backend gateway if required.
• Add registry entry only after the Svelte app is the primary implementation.

apps/grammarAi

Detected:

• Root uses React/TypeScript (App.tsx, index.tsx, vite.config.ts).
• Separate Svelte WebApp at apps/grammarAi/WebApp.

Tasks:

• Consolidate on the Svelte WebApp.
• Convert any remaining TypeScript/React components to Svelte.
• Ensure backend access and translation rules are applied.

apps/taxiBayTreuhand

Detected:

• Next.js + TypeScript app at apps/taxiBayTreuhand/apps/web.
• React Native app at apps/taxiBayTreuhand/apps/mobile.
• Separate API under apps/taxiBayTreuhand/apps/api.

Tasks:

• Define the Svelte target UI (new app required).
• Replace Next.js UI with Svelte.
• Remove or isolate React Native code from the main Svelte-only workflow.
• Integrate API calls via central backend if applicable.

apps/blood

Detected:

• Next.js app at apps/blood (next.config.js).
• Svelte WebApp at apps/blood/WebApp.

Tasks:

• Keep Svelte WebApp as primary.
• Migrate or archive Next.js app.
• Ensure access checks and translations match platform rules.

apps/URL_shorter

Detected:

• Express/Mongoose service (shorterRoutes.js, db.js).

Tasks:

• Create a Svelte UI (or migrate to existing shortener).
• Consolidate backend logic into the central backend gateway.
• Ensure URL shortener uses platform auth and app access logic.

apps/MadeIn/Projekt

Detected:

• SvelteKit + TypeScript (svelte.config.js with adapter, tsconfig.json).

Tasks:

• Replace SvelteKit with plain Svelte + Vite.
• Convert TypeScript to JavaScript.
• Move any client logic/validation to backend.

apps/coffefinder

Detected:

• Svelte app with TypeScript files and SvelteKit-style routes (src/routes/+layout.svelte).

Tasks:

• Remove SvelteKit routing conventions; use plain Svelte + Vite.
• Convert TypeScript to JavaScript.
• Align auth/validation to backend rules.

apps/MemeCoinToken

Detected:

• Static HTML/documents only.

Tasks:

• Decide if this becomes a Svelte app or is archived.

apps/platform

Detected:

• Documentation only.

Tasks:

• Implement as Svelte app or archive.

apps/naviQuiz

Detected:

• Documentation only.

Tasks:

• Implement as Svelte app or archive.