strager

> I think this is wrong. It's not always false. You are correct. We should only warn for `===` or `!==`.

`typeof` is often used to detect if a variable exists in the global scope. We can't *know* what the programmer intended for `typeof` in your example. Can you think of...

Did you want me to review your latest changes, or are you still hacking?

Configuration idea: ```json "warn-if-unused": true // don't warn for let, params, functions, classes, types, ... "warn-if-unused": ["import", "const"] "warn-if-unused": { "/[^_].*/": true, // warn on any variable without a _...

Alternative config idea: ```json "warn-if-unused": true // don't warn for let, params, functions, classes, types, ... "warn-if-unused": ["import", "const"] "warn-if-unused": [ "import", // warn on all unused imported variables {"/[^_].*/":...

`const`

Several websites have editors for JavaScript code. It'd be nice if quick-lint-js could run on these sites. Here's an example of quick-lint-js running in the browser: https://quick-lint-js.com/demo/ This task would...

@Youness-Asserare Based on your performance on other tasks, I think this task is too difficult for you. It's a big project. I leave this task available for others to claim.

I think we can tweak our existing logic for [E0190](https://quick-lint-js.com/errors/E0190/).

For this task, you can look at the logic for either: * E0286/E0287 (`parser::error_on_pointless_string_compare` in `src/quick-lint-js/fe/parse.cpp`), introduced in commit 35207e6616267c6c81be63f47ce97ec2452d60df, or * E0190 (`parser::error_on_sketchy_condition` in `src/quick-lint-js/fe/parse.cpp`), introduced in 1634b9808e0785ca75dbf4fb545a40ee403ebc51. The...