Good point. As you stated, compiler is good at complaining on unused or undeclared variables + it has good style lint as well, so you won't have unused or misspelled classes in CSS. And I should have mentioned that. But eslint is more than just that, it enables consistent code (style can be forced with prettier, but return statements, variable declarations and style, etc). Also, I have just .js files in my project that aren't checked by Svelte compiler.
Ah, I didn't know js files aren't compiled. I thought it processes them so that it can do its treeshaking magic and all.
On the one hand your points make a lot of sense to me and I can relate. On the other hand I wonder whether we (devs) became too spoiled for our own good. We seem to prioritise DX over UX and expect to be hand held (by our free tools and the communities that back them) every step of the way
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.
Thanks you
Good point. As you stated, compiler is good at complaining on unused or undeclared variables + it has good style lint as well, so you won't have unused or misspelled classes in CSS. And I should have mentioned that. But eslint is more than just that, it enables consistent code (style can be forced with prettier, but return statements, variable declarations and style, etc). Also, I have just
.jsfiles in my project that aren't checked by Svelte compiler.Ah, I didn't know js files aren't compiled. I thought it processes them so that it can do its treeshaking magic and all.
On the one hand your points make a lot of sense to me and I can relate. On the other hand I wonder whether we (devs) became too spoiled for our own good. We seem to prioritise DX over UX and expect to be hand held (by our free tools and the communities that back them) every step of the way