Re:Deno 1.4
by golergka on Sunday September 13, 2020 @06:58PM
(#24464648)
For me, two small things that haven't yet been mentioned here.
Dependency management that's much more friendlier to forks. Very often I want to patch something small in a public NPM library and point my company's private project to the fork that contains that patch, not having to wait for the maintainer to accept the PR. Publishing a separate private or public version of this is still a chore.
Typescript support. The current "building" from Typescript to JS is something that mostly works, but still feels icky and sometimes breaks down. Setting up a great debug environment in Typescript/NodeJS codebase is still a pain, and mostly I don't even bother.
I see that none of those are "killer" or seem very important, but it's enough just to try it for some small project in the future. And then, who knows? May be it'll just turn out to be better in general.
Dependency management that's much more friendlier to forks. Very often I want to patch something small in a public NPM library and point my company's private project to the fork that contains that patch, not having to wait for the maintainer to accept the PR. Publishing a separate private or public version of this is still a chore.
Typescript support. The current "building" from Typescript to JS is something that mostly works, but still feels icky and sometimes breaks down. Setting up a great debug environment in Typescript/NodeJS codebase is still a pain, and mostly I don't even bother.
I see that none of those are "killer" or seem very important, but it's enough just to try it for some small project in the future. And then, who knows? May be it'll just turn out to be better in general.