Hi Render,
Deno has matured a ton in terms of node/npm support in the past ~2 years, and now support most things node, which finally makes it a viable option for a many people. With the added benefit of a really strong permission model, and an increased pressure on app security, that’s quite attractive.
I noticed, and used as your customer, the Bun support in Node WebServices that’s enabled through an ENV variable on Render.
I’d like to ask, since it’s been quite a while since this Deno Support ticket, and with the upcoming Deno 2 and LTS releases around the corner, if it’s possible to make a smoother path for Deno installation/usage, similar to the one for Bun, or alternatively have a dedicated Native Environment or maybe just an official guide in your docs with recommended setup instruction.
I’m curious if there is anything technical that makes it harder to make an integration for Deno compared to the one that exist for Bun - because as a server/desktop user the install process seems quite similar.
Also, similar to enabling Bun and Deno, extra points for making it possible to not install Node. When using Deno for security reasons, and meticulously setting the desired permissions, if there’s somehow unintentional calls executed by the Node runtime underneath instead of the symlink to node that deno/bun sets up, I worry that could be a rather stealthy security concern.
Kind regards - and thanks for a great product!
Birk