Deno 2
deno.com
Deno 2
1–10 of 26 posts
Re: Deno 2
#2Full of surprises this October
Re: Deno 2
#3Re: Deno 2
#4(Issues = mts vs ts, configuration problems, lots of conflicting documentation. It doesn't help that I'm mostly DevOps and don't spend every day on writing Lambdas for AWS etc)
Edited to add: The installation page[1] talks about asdf[2] but I find mise-en-place[3] to be faster than asdf.
1: https://docs.deno.com/runtime/getting_started/installation/
Mise/asdf are pretty great. A .tool-versions file in your homedir will set up default versions, and you can override them with .tool-versions in your repos. And because 2 different tools can read those versioning files, you can include them in the repo and pin versions.
Re: Deno 2
#5Re: Deno 2
#6Apart from this little doubt, I love it:
The APIs and std lib are so extensive that we don't need huge amounts of third party packages. Typescript support is great. Deno actually can check Typescript (not just run it by stripping it as Node or Bun). Compiling (bundling) is another great feature.
Re: Deno 2
#7Re: Deno 2
#8I think I wouldn't use TypeScript without Deno now :)
Re: Deno 2
#9I wonder how much Bun pushed them to have full Node.js compatibility.
It's probably more about people complaining they can't run Next or some other framework on Deno which directly impacts their business (Deno Deploy).
Re: Deno 2
#10I found the FAQ in the announcement well made too, with some good and questions and answers.
I'm already having a great time with Deno v1 on my side project - thank you!