The thing with type safety is that systems like typescript are so easy and cheap to deploy, relative to E2E or even unit tests; it’s a small investment that pays off in multiple ways over time (quality, documentation, developer onboarding).
I really struggle to understand the sometimes vehement arguments against it.
Most developers would need to wait until all browsers support it, and the vast majority of users use it, and you could easily be looking at a decade of lost opportunities while you wait for that.
That said, in a world of impending WASM, I don’t even know if TS on the browser makes sense. It seems like it won’t be long and we won’t need a JavaScript intermediary between TS and the browser at all.
I might be wrong (not a front end specialist) but ISTM that a native TS implementation built today would more likely be a compiler to WASM than try to become a first class browser language.
And anyway, direct browser support for TS would take as long as WASM has taken to gain broad support.
We found that our E2E tests took way too long to write and didn’t really cover the visual defects we often hit.
I think our BE engineers are surprised by the lack of testing while at the same time rare runtime exceptions.
We have enough critical flows tested and with TS to prevent runtime errors, we have a decent degree of confidence.
If only we had a good way to test webauthn…
Preach, we had to check the source of the official test suite to figure out how to test it.