How thornedll/utilities works
Project type and purpose
• This is a single‑page application (SPA) built with Create React App and TypeScript.
• It provides client‑side pages for Date conversion, JSON conversion, and JSON diffing.
• There is no backend or microservice; all logic lives in the front‑end within the browser.
File structure
• Top‑level folders:
• public: static assets (index.html, manifest.json, redirects, robots.txt)
• src: application source code
• src subfolders:
• components/UI: reusable low‑level controls (buttons, inputs, tooltips, selects)
• components/blocks: layout pieces (navigation bar, page container wrappers)
• components/pages: individual “routes” or views (DateConverter, JsonConverter, JsonDiff)
• assets/styles: global SCSS modules
• utils, constants, ts (types & interfaces): helper functions and shared types
• Build/config files: package.json, tsconfig.json, CRA wiring (reportWebVitals, react-app-env.d.ts)
README
• Confirms it’s a CRA bootstrapped React/TypeScript project.
• Standard npm scripts: start (dev server), build (production bundle), test, eject.
Diagramming recommendations
• Developer, Dev Server, Bundler, Source Modules, Static Host, Browser
• src → dev server → browser (hot reload)
• src + public → build → deploy → browser
• App.tsx → pages → blocks → UI → browser DOM
• Blue rectangles for code modules
• Callouts for important tech (React, TypeScript, SCSS, CRA).