How jumperexchange/jumper-exchange works
Project type & purpose
• Jumper.Exchange is a full-stack, React/Next.js 13 App-Router application that serves as the web frontend for the Jumper.Exchange service.
• It delivers UI pages, handles client-side interactions (wallet connections, routing, widget flows) and implements backend logic via Next.js API routes.
• It integrates with external blockchain networks, headless CMS (Strapi), Merkl API, analytics (PostHog), error tracking (Sentry), and is containerized & deployed via GitHub Actions to GCP.
High-level file structure insights
• Top-level config & infra:
– Dockerfile, .dockerignore, .github/workflows (build, multi-tag push, deploy to staging/production), .github/actions/init-gcp
– next.config.mjs, gen-api.sh, instrumentation.ts / instrumentation-client.ts, sentry.edge.config.ts, sentry.server.config.ts
• “src/app”: Next.js App-Router pages + layouts, plus “src/app/api” for serverless routes (env-config, profile, widget-* endpoints)
• “src/components” & “src/app/ui”: React component library & page-specific UI
• “src/providers” & “src/hooks” & “src/stores”: application-wide contexts, side-effect logic, global state management
• “src/utils” & “src/lib” & “src/config”: fetch wrappers, URL‐builders, third-party integrations (StrapiApi, MerklApi, RPC shuffling)
• “public”: static assets & manifest
• Tests & storybook: component stories (.storybook), end-to-end & unit tests (Playwright, Vitest)
Extracted deployment & runtime details from README
• Uses pnpm, Vite dev server scripts for different backends (develop, local, staging, production)
• CI/CD pipeline builds Docker image, pushes multi tags, deploys to GCP via GitHub Actions
• Husky, lint-staged, Prettier & ESLint enforce code quality