I'm one of the maintainers of Evidence (open source tool based on markdown + SQL) and working on a similar approach to creating presentation tables configurable in code.
We recently changed our architecture to include interactivity without having to pre-render all combinations. Pages are still pre-rendered with their initial content, but each Evidence app now ships with filter components and an in-browser DuckDB instance so you can build interactive apps. We call this Universal SQL - if you're interested, we wrote up our rationale for doing this here: https://evidence.dev/blog/why-we-built-usql/
You might be interested in Evidence, a SQL-based open source BI tool where all content is version-controllable. Disclaimer: I’m one of the maintainers. A lot of companies use Evidence for customer facing and embedded reporting.
We're fans of Obsidian! DataView looks cool - love the ability to define the tables in code inline in the markdown. That's similar to how we inline DuckDB WASM SQL queries in markdown: https://docs.evidence.dev/core-concepts/queries/
We use ECharts in our open source BI tool (Evidence) and it's a great library. Has helped us build a declarative syntax for viz which can be version controlled (https://evidence.dev)
We used ECharts to build our charting library at Evidence and it’s been a great experience overall (https://evidence.dev).
We started with D3 and a few other tools, but felt that we get a lot more out of the box with ECharts, like interactivity and an events API. ECharts is also a lot more extensible than people give it credit for.