You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wasp should also be checking for required env vars when deployed to production. It happens sometimes to Wasp users that they forget about an env var once they deploy a Wasp app, and then those errors manifest in weird ways, and they have hard time debugging them.
If Wasp server (or client), when deployed, detected that these vars are missing, logged about it and if needed even crashed, it would be very clear that there is an issue and what it is.
Spin off based on this coment: #175 (comment) .
We had multiple people have trouble with this, here is one of the related Discord convos: https://discord.com/channels/686873244791210014/1241745021955473548/1247977812229357668 .
The text was updated successfully, but these errors were encountered: