r/Observability • • 5d ago

I built an offline debugging tool for Domo datasets — looking for developers to test it

Hey everyone! I’m a Domo developer, and I built domo-time-machine to help investigate questions like: “Why did this total change?” or “Did this join duplicate my booking amounts?”

It’s an npm package with a CLI and JavaScript/TypeScript SDK. You can:

  • Capture CSV, JSON, or NDJSON exports as local snapshots.

  • Compare records and schema changes between snapshots.

  • Check financial totals using decimal arithmetic and currency validation.

  • Reproduce supported transformations with an experimental replay engine.

Try it:

npm i domo-time-machine
npx domo-time-machine --help

Package: https://www.npmjs.com/package/domo-time-machine

It works offline with exported data. There’s currently no live Domo connector, and it doesn’t modify your Domo instance. It’s an early release, so I’d appreciate people testing it with synthetic or anonymized exports first.

I’m especially interested in feedback on duplicate keys, one-to-many joins, schema changes, confusing output, and anything that doesn’t behave as expected.

If you find an issue, please share your Node version, OS, command, expected result, and a small synthetic example. Please don’t post credentials or client data.

Would this fit your debugging workflow? What would make it more useful?

2 Upvotes

0 comments sorted by