-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to handle global deno error? #16
Comments
try and catch them try {
const db = await connect({});
} catch (error) {
console.log(error, "skip the connection")
}
const app = new App()
.... |
Hi, I've tested the global Deno error issue. |
I ran into a similar problem when playing around with Deno and MongoDB, and had the same issue. |
I tested with mongodb. |
I guess it's a problem with the Mongo library then, postgres works fine. |
How to keep app running then connection to db was lost? For now deno process is just die.
The text was updated successfully, but these errors were encountered: