Is Deno Ready for Prime Time?

Question

I've been trying to move from nodejs koa to Deno. Increasingly I just can't seem to get there from here. My problems are 1) Deno is not as well supported as Nodejs and 2) I can't figure out which {postgres or upload} modules to use. Deno does not work with managed Digital Ocean managed databases - not because of Deno but because the TLS module is strict. I want to handle file uploads in my Deno server and I can find 4 or 5 different implementations. Which should I use? There are two (at least) Postgres modules.I have found some other instances of people giving up on Deno. This is nothing about Deno, it just seems that Digital Ocean (for example) has made sure they work with Nodejs but not Deno.Looking for motivation to stick with Deno - what has been your experience?

scns · Accepted Answer

For deployment Deno offers it's own service, Deno Deploy:https://deno.com/deployDisclaimer: Haven't used it yet.

revskill · Answer

My main issue with Deno is to support monorepo, or generally how to use local packages.NodeJS might not be the ideal, but it's useful enough to cover real world usecases. Deno is still not useful yet on the DX.

Is Deno Ready for Prime Time?

For deployment Deno offers it's own service, Deno Deploy:
https://deno.com/deploy
Disclaimer: Haven't used it yet.

My main issue with Deno is to support monorepo, or generally how to use local packages.
NodeJS might not be the ideal, but it's useful enough to cover real world usecases. Deno is still not useful yet on the DX.