steinwinde/meek-bank-ui
Watch
1
0
Fork
You've already forked meek-bank-ui
 0
Code Issues Pull requests Projects Releases 4 Packages Wiki Activity Actions
The browser frontend for the meek-bank banking API
157 commits 3 branches 7 tags 2.9 MiB
  • Svelte 81.3%
  • TypeScript 18.4%
  • CSS 0.2%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Felix van Hove 9607640c4d Bump version to 0.4.0
2026-09-17 16:21:01 +02:00
src Bump version to 0.4.0 2026-09-17 16:21:01 +02:00
static First commit to Codeberg. 2026-04-13 15:43:18 +02:00
.env.example First commit to Codeberg. 2026-04-13 15:43:18 +02:00
.gitignore Merge changes from dev branch: 2026-08-21 13:09:07 +02:00
.npmrc Added chart-js, charts, proper status management for products. 2026-05-01 20:34:28 +02:00
.prettierignore First commit to Codeberg. 2026-04-13 15:43:18 +02:00
.prettierrc First commit to Codeberg. 2026-04-13 15:43:18 +02:00
LICENSE First commit to Codeberg. 2026-04-13 15:43:18 +02:00
oauth.md First commit to Codeberg. 2026-04-13 15:43:18 +02:00
package.json Bump version to 0.4.0 2026-09-17 16:21:01 +02:00
pnpm-lock.yaml Added chart-js, charts, proper status management for products. 2026-05-01 20:34:28 +02:00
pnpm-workspace.yaml Setting esbuild builds to false in pnpm-workspace.yaml. 2026-05-25 13:28:42 +02:00
README.md Replace Codeberg reference in README by reference to steinwinde repository. 2026-08-26 09:16:54 +02:00
svelte.config.js First commit to Codeberg. 2026-04-13 15:43:18 +02:00
tsconfig.json Merge changes from dev branch: 2026-08-21 13:09:07 +02:00
vite.config.ts First commit to Codeberg. 2026-04-13 15:43:18 +02:00

README.md

Meek Bank UI

A Svelte browser front-end for meek bank. The two projects share their CHANGELOG.

Developing

Install pnpm. Make sure your meek bank backend is running. Copy .env.example to .env.development. Configure the backend url in .env.development. Start the development server:

pnpm run dev

Building

To create a production version of the app:

pnpm run build

API base URL (cross-origin deployments)

In dev, Vite proxies /v1/* to the backend (see VITE_API_TARGET).

For production or any setup where the API is on a different origin than the UI, set:

  • VITE_API_BASE_URL (example: https://api.example.com)

The UI will then call VITE_API_BASE_URL + /v1/....

If the API is cross-origin, ensure the backend CORS policy allows:

  • Authorization header
  • the UI origin
  • required methods (GET/POST/PATCH/DELETE)