I’m curious about the value of eslint for TypeScript. I’ve not really found myself wanting from the coverage provided by tsc.
I use eslint for things like catching left behind debugger and console statements.
Starting a TypeScript Project in 2021
11–20 of 190 posts
Re: Starting a TypeScript Project in 2021
#12In 2021, I think it's safe to start a TypeScript project with Deno.
Doesn't that depend on what libraries you need?
Re: Starting a TypeScript Project in 2021
#13Casting window to any in a pinch does work. But for longer term stuff, it's probably better to extend the Window interface.
Re: Starting a TypeScript Project in 2021
#14Nice article, you could also just use https://github.com/formium/tsdx
I looked at TSDX for a project and was rather put off by the fact that:
* It hasn't been updated for six months
* It doesn't appear to support TypeScript 4 properly[1]
Re: Starting a TypeScript Project in 2021
#15Ava (https://github.com/avajs/ava) gets too little love from the blogging machinery. It's a breeze to use with TS, faster than Jest (YMMV of course), and I love the snapshot output over any other snapshot producing unit test tool. Use with NYC for coverage is a breeze.
Re: Starting a TypeScript Project in 2021
#16Earlier quoted context omitted.
Does Deno work for frontend?
No it's a replacement for Node.
Please stop spreading this misnomer. It's an alternative platform. It's absolutely not a wholesale replacement, and its inner workings are vastly different to Node.
Edit: Well, someone touched a nerve! Doubt me, downvoters? You need but google to find a wealth of information to support the statement. https://www.imaginarycloud.com/blog/deno-vs-node/ is the first result, and there are a litany of other articles explaining the same.
Re: Starting a TypeScript Project in 2021
#17I’m curious about the value of eslint for TypeScript. I’ve not really found myself wanting from the coverage provided by tsc.
The larger the pool of engineers on a project (or the larger a team size) the more important consistent formatting becomes. It may not be relevant for individual projects (though I'd disagree with that as well), but it makes maintenance of projects under larger teams, including distributed teams, a heck of a lot easier.
Re: Starting a TypeScript Project in 2021
#18I’m curious about the value of eslint for TypeScript. I’ve not really found myself wanting from the coverage provided by tsc.
e.g. ban `any`, which you cannot do with tsc.
Re: Starting a TypeScript Project in 2021
#19I’m curious about the value of eslint for TypeScript. I’ve not really found myself wanting from the coverage provided by tsc.
IDE integration is one benefit, as in VS Code showing the linting issues without compiling.
Re: Starting a TypeScript Project in 2021
#20Earlier quoted context omitted.
No it's a replacement for Node.
Please stop spreading this misnomer. It's an alternative platform. It's absolutely not a wholesale replacement, and its inner workings are vastly different to Node. Edit: Well, someone touched a nerve! Doubt me, downvoters? You need but google to find a wealth of information to support the statement. https://www.imaginarycloud.com/blog/deno-vs-node/ is the first result, and there are a litany of other articles explai…
> Please stop spreading this misnomer.
That's a fairly… direct way of putting it :-)
Anyway:
1. What are the key differences in terms of usage and use cases?
2. Why isn't Deno a 'wholesale' replacement for Node?
3. In which respect are the vastly differently inner workings relevant in regards to usage of both products?