Perception apps
This repository contains six applications, a shared application launcher, a navigation page, and a platform-neutral static deployment bundle managed through one npm workspace:
compound-interest-calculatorhousing-affordability-calculatorkrisflyer-spontaneous-escapestrading-courseus-compensation-comparesg-electricity-savings-calculator
Requirements
- Node.js 26.0.0 or newer
- npm 10 or newer
Install
Install all dependencies once from the repository root:
npm install
Development
npm run dev:compound
npm run dev:housing
npm run dev:escapes
npm run dev:trading
npm run dev:compensation
npm run dev:electricity
npm run dev:navigation
Validation
npm run build
npm run test
npm run typecheck
npm run lint
Build the combined site
npm run build
npm run verify:site
The combined static site is written to dist/ with this URL structure:
/ — application navigation/compound-interest-calculator//housing-affordability-calculator//krisflyer-spontaneous-escapes//trading-course//us-compensation-compare//sg-electricity-savings-calculator//_shared/app-navigation.js — the independently built React application launcher
The assembler injects the shared launcher into each compiled application's index.html. The launcher renders inside a Shadow DOM to isolate its styles from every application. Because it is built and cached separately, launcher-only changes do not require rebuilding unchanged applications.
The output uses relative asset paths, so the entire dist/ folder can be deployed to most static hosting platforms without provider-specific configuration. Use npm run preview after building to test application switching across the complete site.
Continuous integration
GitHub Actions builds the application launcher and each application independently, then publishes one deployable-site artifact. Each compiled output is cached by its own source and dependency hash. If an application is unchanged, its existing output is restored and its install, validation, and build steps are skipped. Changes to the root package files invalidate every application cache because shared dependency changes can affect every build.
Download the deployable-site artifact from a completed workflow run and upload its contents to the static host of your choice.
Pushes to main and manual runs on main also deploy that verified artifact to the Cloudflare Pages project named by the CLOUDFLARE_PAGES_PROJECT repository variable. Pull requests never deploy. GitHub stores the Cloudflare account ID and API token as repository secrets.
The electricity tariff refresh runs at quarter boundaries, commits validated SP tariff history to JSON, and explicitly dispatches the existing deployment workflow when data changes. See sg-electricity-savings-calculator/README.md for its schedule and calculation rules.
