Developer reference
Technology and versions
Understand Helm’s separate app and documentation toolchains and where exact versions are recorded.
The financial app and documentation are independent packages. Install and build them with their own lockfiles; they intentionally use different Next.js major versions.
Package boundaries
| Package | Main stack | Runtime role |
|---|---|---|
| Application | Next.js 16, React 19, TypeScript | Public pages, private financial UI and API. |
| Documentation | Next.js 15, Nextra 4, React 19 | Public MDX guides and Pagefind search. |
| Data and identity | Supabase Auth and PostgreSQL | User identity, ownership and financial persistence. |
The release toolchain is Node 22.23.3 and pnpm 11.2.2. Exact dependency versions are in each package’s package.json and pnpm-lock.yaml.
Where work happens
React components and API helpers run the inquiry UI. Server services handle financial reads and commands. Workbook and text-PDF parsing run on the server; supported format recognition still requires preview and explicit recording consent.
The docs can build without financial credentials. Its only public origins are the app and docs links. A docs dependency upgrade should not alter the application dependency tree.
Before upgrading
Review both lockfiles, the package’s own scripts and the affected runtime boundary. Run the relevant quality checks, including a compiled documentation search check if the docs framework changes. A source test does not exercise native PDF or workbook runtime support.
Start with installation for a clean local setup.