Running the application locally

[gokullan]

Hi!
I am trying to build and run (locally) the React SPAs such as dashboard-app, autocomplete, etc.. However, I am facing some issues:

• The README in the SPA directory mentions a build-ts.sh script under the proto directory, but I'm unable to locate this script. Is this auto-generated via some command? (I have already done pnpm install in the proto directory).
• I ignored the above step and proceed to do the rest - the build is successful and the SPA (in my case dashboard-app) also starts up, but I am getting a blank page on http://localhost:3433/. In the console, I can see errors that say Fig.js is not supported in this browser. How do I resolve this?
• Am I supposed to run SPAs this way or do I need to do something else?

Specifications

OS: Arch-linux (Kernel 6.12.21-1-lts)
Architecture: x86_64
Browser: Firefox (137.0-1)
Source-code version: The current main branch.

[uldyssian-sh]

The two issues are separate: the missing build-ts.sh step and the blank page / “Fig.js is not supported in this browser”.

1. Missing proto/build-ts.sh
   That script is typically an old convenience wrapper that used to generate TypeScript client/types from protobuf (or similar “proto” artifacts). In many repos it gets removed over time and replaced by a package.json script (for example, pnpm run gen, pnpm run build:proto, pnpm run codegen, etc.).

What to do:

• Treat the README reference as outdated.
• Use the scripts defined in proto/package.json instead of looking for build-ts.sh.
• The “right” replacement is whatever script generates TS artifacts from proto definitions and writes them into the locations consumed by the SPAs.
• After running that codegen script, rebuild the SPA.

Practical command pattern (adapt to whatever scripts exist in proto/package.json):

• pnpm -C proto install
• pnpm -C proto run <codegen-script>
• pnpm -C dashboard-app run dev (or the SPA you want)

2. Blank page + “Fig.js is not supported in this browser” (Firefox)
   This usually means the SPA is trying to load a browser capability that is not available in your current browser/runtime configuration. Most commonly it’s one of:

• reliance on Chromium-only APIs
• WebAssembly threads / SharedArrayBuffer without cross-origin isolation headers
• a dependency that explicitly supports only Chromium-based browsers

What to do (most reliable):

• Run the SPA in a Chromium-based browser (Chrome/Chromium/Edge) for local development.

If you must use Firefox:

• Ensure the dev server sets the required cross-origin isolation headers, because SharedArrayBuffer / wasm threads require them:
  • Cross-Origin-Opener-Policy: same-origin
  • Cross-Origin-Embedder-Policy: require-corp
• Once those headers are present on localhost, reload and the Fig.js/wasm-thread related errors typically disappear (if the library supports Firefox at all).

3. “Am I supposed to run SPAs this way?”
   Yes: build the shared proto/types first (via the proto codegen script), then start the SPA dev server.
   If codegen is skipped or outputs aren’t where the SPA expects, you can still “start” the SPA but it will render blank or crash early.

Summary of the correct local flow:

• Run proto/type generation using the scripts in proto/package.json
• Rebuild the workspace
• Run the SPA dev server
• Use Chromium by default (or add COOP/COEP headers if Firefox is required)

[uldyssian-sh]

Thanks! If this helps, please consider marking it as “Helpful” or “Accepted” 😊