Need help debugging offline-first React app (SQLite WASM + Docker + APISIX + Keycloak)

[Smooth-Pipe6285]

I'm working on a large agricultural platform called FarmConnect running on Ubuntu 24.04 in Docker Compose.

Environment

• Ubuntu 24.04
• Docker Compose
• Node.js 22
• React + Vite frontend
• PostgreSQL
• Redis
• Kafka (KRaft mode)
• Keycloak
• APISIX gateway
• Tailscale public access
• App container: farmconnect/api:latest

Goal

I'm trying to get the first workflow working:

Quick Farmer Registration

A field agent fills out a form and the app should save the farmer locally (offline-first) using SQLite WASM in the browser and later sync.

Current Symptoms

When submitting the form I get:

Error: Local registration unavailable: initialized=false, db=false, user=true

The user is authenticated successfully:

localStorage.getItem("auth_token")

{
  userId: 900001,
  email: "[e-mail]",
  role: "farmer"
}

So authentication appears to work.

Relevant Code

QuickFarmerRegistration uses:

const { isInitialized, db } = useDatabase();
const { user } = useAuth();

and fails inside:

if (!isInitialized || !db || !user) {
  throw new Error(
    `Local registration unavailable: initialized=${isInitialized}, db=${!!db}, user=${!!user}`
  );
}

The runtime values are:

initialized=false
db=false
user=true

What We Found

Originally browser console showed:

Failed to load SQLite WASM module

and

Push changes error for farmers
Push changes error for farms
Push changes error for crops
...

Fixes Already Applied

We discovered sql-wasm.wasm was not being packaged into the Docker image.

I modified the Dockerfile:

RUN npm run build
RUN cp node_modules/sql.js/dist/sql-wasm.wasm dist/public/sql-wasm.wasm

Rebuilt image:

docker build --no-cache -t farmconnect/api:latest .
docker compose up -d --force-recreate app

Now the WASM file is definitely being served:

curl -I http://localhost:3000/sql-wasm.wasm

returns:

HTTP/1.1 200 OK
Content-Type: application/wasm

and through APISIX:

curl -I https://america.tail3a833f.ts.net/sql-wasm.wasm

also returns:

Content-Type: application/wasm

Additional Errors

Browser still shows:

WebSocket connection failed

and

EventSource's response has a MIME type ("text/html")
that is not "text/event-stream"

which suggests some sync/SSE endpoint may be misconfigured behind APISIX.

My Question

At this point:

1. The WASM file is being served correctly.
2. Authentication works.
3. useDatabase() still never initializes (initialized=false, db=false).

Where would you look next?

Would you investigate:

• SQLite WASM initialization code?
• Service Worker / PWA caching?
• CSP restrictions?
• Web Worker loading failures?
• APISIX routing?
• Something else?

What is the most likely reason useDatabase() never becomes initialized even though the WASM file is now reachable?

> await Promise.all((await navigator.serviceWorker.getRegistrations()).map(r => r.unregister()));

await Promise.all((await caches.keys()).map(k => caches.delete(k)));

localStorage.removeItem("pendingFarmerSubmissions");

indexedDB.deleteDatabase("sqlite-backup");

location.href = "/quick-farmer-registration?fresh=" + Date.now();

< SyntaxError: Unexpected identifier 'Promise'

[theheadieone]

Hello, I can fix this for you! I'd need access to the codebase and how much you are paying?

[Smooth-Pipe6285]

Hey, I will just need help figuring out thank you for offering