Do you really need TypeScript in Dataverse?

Do you really need TypeScript in Dataverse?

Do you bring a tank to a Nerf gun fight?

Most form scripts in PowerApps Model-Driven Apps are tiny: - Show/hide a field - Trigger a lookup filter - Or yell at users when they enter garbage

💡 These are not complex apps. They’re micro-patches for the UI.

And you're not even allowed to touch the raw HTML. You can only work through the official SDK — no DOM party tricks here.

So... TypeScript? - You add a build pipeline - You compile before testing - You write type annotations for functions you barely use twice - You debug through source maps, not your actual code

All for a script that’s 50 lines and can’t even leave the form it was born in.

Modern JS already gives you: - let, const, arrow functions - ?. and ?? for clean null checks - async/await pattern - Template strings and object destructuring

Want type hints? Use a bit of JSDoc and enjoy 90% of the benefits.

Unless you: - Build shared libraries - Write form logic for 20+ entities - Or maintain a long-term complex project... - With a lot of team members

Then yes, TypeScript 'could' help.

But if you're just poking a form to behave itself? Stick to JS: Keep It Stupid Simple!

👉 What’s your take: TS or JS for Model-Driven Apps?