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.
5 Replies
I think it’s only validating env vars. Is that right @Wasp Team ?
@Chris Paliqaw what version of wasp are you on?
What kind of errors did you get?
Check his other question
Is the script "validate-env.mjs" somehow attempting to validate the TypeScript of external libraries?That should be a no but I'll have to double check with your exact repo. The validation script lives in a separate world (it doesn't import user code) and it doesn't rely on Typescript. The more likely explanation is that the issue happens while the Typescript compiler compiles the code for deployment errors, but the error is right after the validation script outputs some text.
soudns reasonable to me also