Replies: 1 comment
-
(copying my earlier response from the initial issue to this discussion) There's no question about it; for Deno, it is better to use a library specifically made for Deno. It will use modern, mostly standard APIs Deno is built around, so they likely have cleaner, more efficient codebase, and more "modern" API. Also the additional complexity of node compatibility layer is avoided. However, like with any library, one needs to be mindfull of how well any given library is maintained and supported. Node has been around for a long time, and is very popular. Thus many npm libraries are more mature compared to the relatively young Deno libraries that may have some bugs, missing features, and smaller community of forward-looking developers doing the legwork of ironing all the small issues out. So, I suggest choose the Deno library by default. If that is incomplete or doesn't work out for you for some reason, only then fall back to the NPM version. |
Beta Was this translation helpful? Give feedback.
-
With introduction of the NPM-compatibility in Deno.js, a developer can chose wherever to use an NPM-module or a suitable Deno.js library, e.g.:
or
In case there are alternatives, which version should a developer prefer?
This question especially relevant for linters, where from one side we have ESLint — a proved and currently the most advanced JS linter with extremely wide community and active development cycle with releases about every two weeks, and from the other — Deno Linter with a limited ruleset.
P.S. By mistake, initially, I've opened an issue on the subject.
Beta Was this translation helpful? Give feedback.
All reactions