Deno is not a drop in replacement for nodejs, which is a pity.
Deno is not a drop in replacement for nodejs, which is a pity.
I like Deno specifically because of how different it is from node.
I'd love to hear what problems did you hit and look into solving them.
Is there a written guide for how to convert a nodejs project to Deno?
I'd really prefer to be using deno instead of node. If it was a seamless experience I would definitely drop nodejs.
Eg. if you have a Vite app (or any other app really) with "package.json" and some "scripts" defined there, just try running "deno task <script_name>". Deno will automatically pick up "package.json" and try its best to run the that script.
It's not fully done, but in our testing we got a lot of non-trivial projects running that way. If something doesn't work in your case, I would greatly appreciate a bug report to help us fix this.
As for the written guide - there's not a single one at the moment - it's something we'll be looking into in the coming months.