Support for Deno

[ajile-in]

Feature Request

Now that it has been announced that Deno 1.0 will be released the 13rd of May 2020.

So maybe it's time to consider this?

Is your feature request related to a problem? Please describe.

Nope. When Deno 1.0 releases in the May, it would great to start using it with NestJS.

[BrunnerLivio]

As from denoland/deno#2644:

It's unlikely we can make Node code work 100% of the time. But we can do a lot to make porting modules over easier.

Deno is in my opinion not mature enough to even attempt to port NestJS to it at the current time. I'd suggest we first see how it evolves with "smaller"-ish Node.js projects - whether they get ported or rewritten. Depending on the trend or "standard" which will be set by the community we would then consider moving along with NestJS.

But in all fairness - Deno is a different thing. I want to respect its philosophy, style guide and direction. NestJS was built using the Node.js philosophy. Porting NestJS 1:1 would be like putting a penguin into a pond of fishes. It may work -- its just really odd.

Note; I am actually a huge Deno supporter and been following the community since day 1. In fact, I have already published some resources for Deno. I just want to be realistic and rather pragmatic here.

[kamilmysliwiec]

As @BrunnerLivio, let's see how Deno evolves over time. If the community grows rapidly, I'll certainly consider porting several core mechanisms to Deno, respecting their style guide and conventions. It doesn't make any sense at this point though.