TypeScript checking by "wasp deploy fly deploy"?

This is a similar topic to my question "Deployment failure on fly.io", but I wanted to have a separate thread so the issue is more easily searchable in the future. Is the script "validate-env.mjs" somehow attempting to validate the TypeScript of external libraries? I'm not sure if this is intentional or not. I would ask that this be turned off, and leave the validation of their own TypeScript to the external libraries. In my specific case, the TypeScript in the Viam library may actually be ok, but perhaps the convoluted boolean expression confused the TypeScript checker.