|
|
|
|
|
by suriya-ganesh
150 days ago
|
|
unfortunately this is not the most common practice. I've worked on rust codebases with 10K+ warning. and rust was supposed to help you. It is also close to impossible run any node ecosystem without getting a wall of warnings. You are an extreme outlier for putting in the work to fix all warnings |
|
Haven't found that myself, are you talking about TypeScript warnings perhaps? Because I'm mostly using just JavaScript and try to steer clear of TypeScript projects, and AFAIK, JavaScript the language nor runtimes don't really have warnings, except for deprecations, are those the ones you're talking about?