Deno supports Typescript. And Typescript supports Typechecking without a build process.
Linters, tests and other tools can also be run without a build process.
What exactly is "a build process" for you. For me, it is a process which results in an artifact. An artifact that is, in the best case, automatically tested, optimized, signed, and ready to be deployed. Compilation is a rather small part of it. But since I need to run all the other things anyway, why not compile there, and remove entropy from runtime.
"build process" is defined in detail in TFA. You're arguing about something so entirely orthogonal to the point of the article that I can't help but wonder if you've actually read it.
I did read it, and I find the title misleading.
I think that the absence of a compilation phase does not prevent the establishment of infrastructure for e2e testing. If you can only be sure that the application is running when the build is successful, then there are probably other big problems there.