supabase-js try/catch Doesn't Catch Errors: Check { error }
Conclusion supabase-js query methods never throw on network or PostgREST failure. The contract template's current-version resolver branched only on whether data was present, without ever looking at the error that came back alongside it. That meant a transient read failure couldn't be told apart from "no row has been published yet" — and when that return value fed a version-freeze decision, it…
The supabase-js query methods did not handle network or PostgREST failures properly. The contract-template resolver would not distinguish between a transient read failure and a lack of published rows, which could freeze an outdated version that the customer had not agreed to. To fix this, the affected code was refactored into a dedicated function called readCurrentRow, which explicitly checked for errors and returned a tuple containing the row data and a failed flag.
The getContractMeta function was updated to branch on this failed flag, allowing it to return null and freeze no version when the read itself failed. This ensures that only stable, agreed-upon versions are used in the signing flow, preventing auto-renewal clauses from being applied without proper contractual basis.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.