How vikydealewen/coin-bank-system works
Project type and purpose
• This is a full-stack web application consisting of:
• A front-end SPA (“Coin Bank”) built with vanilla JS, Webpack, Babel, SCSS, Navigo for routing, Chart.js for charts, Choices.js for custom selects, and Yandex.Maps for ATM display.
• A backend Node.js/Express service (in backend/) that exposes REST-style endpoints and serves static JSON data (public/data.json).
• End-to-end testing via Cypress.
File structure
Top-level directories:
• src/ – SPA code, subdivided into:
– modules/ (API client, routing, utilities)
– components/ (reusable widgets: header, select, spinner toggle)
– pages/ (feature pages: login, accounts list, account details, history, currency exchange, ATM map)
– main.js + main.html (SPA entry point)
• backend/ – Node.js service with src/index.js (server entry), cards.js (controllers), utils.js, and a public/ folder for static JSON.
• cypress/ – E2E tests, fixtures, support files.
• Configs: Webpack (webpack.config.js), ESLint/Prettier/Stylelint, Cypress config.
README for additional insights
• SPA features: login, account creation, transaction history, transfers, currency exchange, ATM map.
• Requires the backend service running.
• Dev server runs on port 4000, builds to dist/ for production.
• Test runner: Cypress uses the SPA + backend.
Detail
• Sub-domains: routing layer vs feature pages vs shared modules
• Build pipeline if relevant (Webpack → bundle → served)
• Port numbers (Dev: 4000 for frontend, backend port from backend/README)
• User flows: Login → fetch accounts → view history → perform transfer → update UI