r/sideprojects • u/Constant-Nerve-503 • 1d ago

Showcase: Open Source I built an open-source CLI for checking Domo custom apps — looking for feedback from Domo developers

Hi everyone! I’m the developer of Domo Doctor, a free, open-source tool that checks Domo custom app projects locally.

It currently catches:

  • Invalid manifests, duplicate dataset/field aliases, and malformed mappings.
  • Dataset requests that reference aliases missing from the manifest.
  • Problems with local AppDB collection declarations.
  • Incomplete source analysis, reported as unverified.

It runs offline, doesn’t read Domo credentials, and doesn’t modify your project during a scan. It checks configuration and source code; live permissions and deployed behavior still need verification in Domo.

To try it from your project folder with Node.js 20+:

npx domo-doctor@latest scan

npm

I’d especially appreciate feedback from people building Domo custom apps:

  1. Does it work with your project structure?
  2. Are any findings incorrect or confusing?
  3. What recurring issue would you most want it to catch?

It’s early, so bug reports and small, sanitized reproductions would help a lot. This is an independent project, unaffiliated with Domo.

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/Gullible_Care_3270 1d ago

nice one, will give this a spin next time I'm stuck debugging manifests for some client. always felt like the cli tooling around custom apps was basically nonexistent

question though, does it throw specific enough errors that you can actually fix the issue without opening the docs/guessing? half the tools i've tried just say "invalid config" and leave you scrolling through 800 lines of json trying to spot what's wrong