Unify the native shell and harden it:
- src/config.ts: single source for local host/port, preference keys, secure-storage
key, timeouts, and CSRF constants (dedupes LOCAL_URL etc. across App/LoadingScreen).
- src/api.ts: one HTTP client — credentials mode, AbortController timeouts, and error
normalization into user-facing messages (network/timeout/401/403/429/5xx), with typed
auth responses.
- Batch 10 CSRF fix: /api/auth/totp/challenge is not CSRF-exempt, so the native TOTP
step now fetches GET /api/auth/csrf-token and echoes it as x-csrf-token (mirrors the
web client); TOTP login no longer breaks for 2FA users.
- Error-handling / boot robustness: LoadingScreen gets a health-poll timeout and
surfaces main.js's {type:'serverError'} channel messages instead of spinning forever;
App.tsx bootstrap and the encryption-key fetch now .catch to a visible state; crypto.ts
reports secure-storage failures.
- Data safety: move the SQLite DB, backups, and tmp OUT of nodejs-project into the app's
filesDir (bt-data). nodejs-mobile re-copies nodejs-project on every app update, which was
silently wiping local-mode data. Verified on the emulator: create data -> bump versionCode
-> reinstall -> migrations skipped, no re-seed, data persists.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The web app migrated its server to TypeScript (server.cts) on Express 5 /
openid-client 6 / kysely, none of which ran on the old embedded Node 12.19.
Rebuild the local-mode pipeline for Node 18:
- sync-nodejs-project.sh: sync server.cts + .cts/.mts + setup/ + seed data.
- transpile-node18.js (replaces transpile-node12.js): esbuild TS->CJS in place,
keeping .cts/.mts filenames (Node 18's CJS loader loads unknown extensions via
the .js handler, so the explicit-extension require() graph keeps resolving).
- prepare-local-mode-deps.js: bundle ESM-only kysely to CJS, stub openid-client
(unused on-device), and rewrite path-to-regexp's \p{} regexes to ASCII (the
no-ICU Node 18 build can't compile unicode-property escapes).
- build-better-sqlite3-node18.sh (replaces the Node-12 build/fix scripts):
cross-compile for all three ABIs against the Node 18 ABI, injecting libnode.so
as a NEEDED entry so V8 symbols resolve at dlopen.
- main.js: entry -> server.cts; drop the now-native randomUUID/hkdfSync polyfills
(keep the Intl shim); add TMPDIR + a startup-error relay to the WebView.
- nodejs-project/package.json: server dep set matched to the web app.
Verified end-to-end on the x86_64 emulator: boot -> migrations -> seed -> login
-> create bill -> force-stop -> relaunch -> data persists. arm64/armv7 prebuilds
are built and link-verified; a physical-device run is still pending.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Swap the abandoned nodejs-mobile Node 12.19 runtime for the nodejs-mobile core
Node 18.20.4 Android build, staged into the plugin by install-node18-runtime.sh
(the cordova fork's Android side is still Node 12). Re-register the cordova-bridge
linked binding via explicit napi_module_register(NM_F_LINKED), since Node 18's
NAPI_MODULE_X macro drops the flag and process._linkedBinding could no longer
find it. Verified on the x86_64 emulator: process.version=v18.20.4 and a full
native<->node channel round-trip (device encryption key delivered).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Capacitor + React + Vite app for Android
- SetupScreen for server URL connection or local mode
- LoadingScreen with nodejs-mobile health polling
- sync-nodejs-project.sh: --source flag (defaults to ../bill-tracker)
- transpile-node12.js: uses own esbuild devDependency
- prepare-android-assets.js: nodejs-mobile cordova asset packaging
null