CLI tools is among the things I create. Either way, I'm not the one making it complicated, TS compile-step is making it complicated, JSDocs is making it uncomplicated. Admittedly, ESLint was pretty easy, but I use a different test-runner and my fight was also with Storybook, but it has been a while, maybe it has improved. Anyway, it doesn't matter, my point is that you cannot deny that if you move from JS to TS files, you will need to make all of your devtools, whether that's testing, linting, demoing, whatever, compatible with your compilation-step. We can argue about how much effort it really is, or should be, the point is that it's always less effort if you don't need to introduce the compilation-step. You might not like the JSDocs comment syntax, you may not like writing some types in separate hand-written .ts or .d.ts files to import into your JSDocs comments, but the dev setup overhead is certainly a lot less, and moving to a new tool is a lot simpler as you don't need to think about the compilation-step.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
CLI tools is among the things I create. Either way, I'm not the one making it complicated, TS compile-step is making it complicated, JSDocs is making it uncomplicated. Admittedly, ESLint was pretty easy, but I use a different test-runner and my fight was also with Storybook, but it has been a while, maybe it has improved. Anyway, it doesn't matter, my point is that you cannot deny that if you move from JS to TS files, you will need to make all of your devtools, whether that's testing, linting, demoing, whatever, compatible with your compilation-step. We can argue about how much effort it really is, or should be, the point is that it's always less effort if you don't need to introduce the compilation-step. You might not like the JSDocs comment syntax, you may not like writing some types in separate hand-written .ts or .d.ts files to import into your JSDocs comments, but the dev setup overhead is certainly a lot less, and moving to a new tool is a lot simpler as you don't need to think about the compilation-step.