3 ms·
Almost a year ago with Deno 1.22 type checking for TypeScript was default disabled. (i.E. you must manually request checking on the CLI, editors still do typech
by SyrupThinker 4y ago
Almost a year ago with Deno 1.22 type checking for TypeScript was default disabled.
(i.E. you must manually request checking on the CLI, editors still do typechecking as before)
At least in my microcosm of Deno-use the package quality degraded since then with more and more packages having subtle type bugs that could have been caught easily by anyone with checks enabled.
Compared to what was before that is to me a drawback, but of course it depends on whether your bigger priority is to reduce friction.
Apparently `deno bundle` has now been deprecated too, because it couldn’t be used for web bundling and because NodeJS support is hard.
So early adopters that possibly wanted to get away from the web and NPM get punished by these ecosystems now.
Hope my 2 cents answer your question.