How johnwongapi/helm-decode works
Project Type & Purpose
• This is a single-page, client-only React/TypeScript application packaged with Webpack, served statically (GitHub Pages).
• Purpose: Offline, in-browser decoding of Helm3 Kubernetes secrets; no server or backend calls.
Core Components
a. Frontend React Application
• Entry point: public/index.html → src/index.tsx → App.tsx
• UI Components:
• HelmDecode.tsx: input/output area and decoding logic hooks
• Ref.tsx: reference/help panel
• Utilities: helmDecoder.ts (actual decode algorithm), defaultInput constant
• Styles: App.css
b. Build & Deployment Pipeline
• Webpack (webpack.config.js) bundles TSX/JS, CSS, assets
• TypeScript compiler (tsconfig.json)
• NPM scripts (package.json) for “start”, “build”
• GitHub Actions workflow (deploy-to-gh-pages.yml) pushes build to GitHub Pages
c. Hosting & Delivery
• GitHub Pages serves the static files from the “build”/“public” output
• Users access via https://helm-decode.jojo.hk
Relationships & Data Flows
• Developer → (git push) → GitHub Actions CI → Webpack build → GH Pages
• End-User Browser → fetch static assets → executes React app
• In-Browser → user inputs secret → helmDecoder util runs client-side → output displayed immediately
Architectural Patterns & Principles
• Single-Page Application (SPA)
• Client-side only processing (zero-trust of network)
• Component-based UI (React)
• Continuous Deployment via GitHub Actions
• Strict separation:
• Source code (src/)
• Public assets (public/)
• Build config & scripts
Essential Elements Checklist
• [ ] Components: React App, CI/CD, GitHub Pages, Browser
• [ ] Sub-components: UI modules, util functions
• [ ] Build & runtime axes (e.g., left side build pipeline, right side client runtime)