Deno 1.10 Release Notes
Still not tempted by Deno to be honest.All the problem that currently exist in Node are being ported to Deno straight up.The built-in apis provided by Node.JS are almost non-existent... hence most of them are buggy and quiet tedious to use , it's why the community has created thousands of packages to resolve those issues.Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of having 1000+ dependency from NPM you'll have 1000+ dependency from remote URL with everything set at "read/write" because they need to read one file from your ".env" folder or perform an arbitrary post install process...The way Ryan managed Node and how the ecosystem as turned to chaos because of is lack of vision and strategy make me not want to try any of it's tech again. Ryan is the kind of guy that gets obsessed over ONE THING and goes berserk for 5 years on that topic until he overdose and quit abruptly.I don't think that's how you manage a language , when I look at Zig I'm way more confident of what's being done that the current state of Deno...Node.JS is one of my main language , but the ecosystem around it is an absolute disaster.