I have been waiting for this release for the new possibility to include a comment in eslint-disable-{next-}line:
// eslint-disable-next-line no-console -- Here's a description about why this configuration is necessary.
console.log('hello');
I haven't done TypeScript/JavaScript in a while. What's the status of ESLint taking over from TSLint (for both the tool itself and the vscode extensions)?
Ah ESLint, the most necessary bane of my existence. Good work to the team for the update.
Hopefully it got a little less „dependency-heavy“ than before. Using eslint and babel tends to add 200mb of dev dependencies to a project...
Does anyone know if they have addressed the major performance problems with typescript?
This was a few months ago, but tslint takes a few seconds on one of our larger code bases. However ESLint with the typescript plugin would take up to a minute+, and seemed to make webstorm struggle with the eslint integration.
I know the whole "there are two types of programming languages" Stroustrup quote applies to JS just as much as it does to C++, but can anyone comment on whether JS was hated as much as it was back when this second generation of browsers was being built? As someone who went straight into research and low-level work, I don't touch JS very often, but it seems to me as though the Web is in this arranged marriage it doesn't like, but refuses to leave because of the inconvenience.
I feel like in some regards, we have seen generational shifts in other languages. In domains where Perl, Java, and C++ used to dominate, we now have Go, Rust, and Python.
Absolutely worth noting that with the exception of Python, there are probably still vastly more lines of C++/Java code running in production than Go/Rust. I kind of don't get how if JavaScript is so bad, then why do we now have things like Node?
Sad to see that bundled packages with shareable config are still not supported :(
Does this release support Yarn v2’s Plug’n’Play?
There is a rule in eslint that warns you when a promise is dangling and hasn't been handled.
Please use that rule. So many bugs in the JS world is because of dangling promises.
I didn't like programming in JavaScript so much because I think the syntax makes it a little harder to read than necessary.
However, I confess that after adopting ESLint in my workflow, things have improved considerably. I can ask it to warn me on unused stuff, to enforce the lack of semicolons, to format and indent my code correctly on save... it's a very useful tool. If you have something against JavaScript in general, give it a try.