3 ms·
I think it's to maximize potential contributor base. JS is the front-end browser language. That's its origin story and it almost certainly will always have tha
by NateEag 4y ago
I think it's to maximize potential contributor base.
JS is the front-end browser language. That's its origin story and it almost certainly will always have that job, because of web browser backwards compatibility.
That's why it's so universally known / used / understood.
Once you target TypeScript you're suddenly looking at a much smaller set of devs who know it, and you're married to a language that's effectively owned by a single company (MS, to boot).
You can get decent gains in type-checking by writing JSDoc and using tsc in your build process without adding much friction for new contributors.
- tonto 4y agoI think its more that eslint at its core does not support typescript and they want to run the eslint tool theyre developing over the eslint codebase. It's hard to argue with this but it doesnt seem like the greatest outcome
- madeofpalk 4y agoI would guess that more people know how to write Typescript than annotate with JSDoc.
- ohbtvz 4y agoThe kind of people who'd be willing to contribute to eslint are very probably not afraid of writing in typescript.