Rule extract-sequence-expressions fixes can be incorrect

The rule: extract-sequence-expressions

Often has issues fixing sequence expressions that include extra parenthesis or function calls.
I does well to identify the issues, but fails in fixing them. For example:

Example: localStorage.setItem('country_code', s), (global.$stores.useCookieConsent = !t.includes(s));

This will produce the output below

Bad Output: localStorage.setItem('country_code', s, (global.$stores.useCookieConsent = !t.includes(s)));

It should produce the following output.

Expected Output: localStorage.setItem('country_code', s); global.$stores.useCookieConsent = !t.includes(s);

[coderaiser]

I cannot reproduce the nodelete and _ cases. Could you please re-install 🐊Putout with:

npm i putout

And try again. Is it works for you now? The case with await should work as well 😃.

[coderaiser]

Just lander ability to convert sequence call expressions in @putout/plugin-extract-sequence-expressions@3.3.0.

With await is a bit harder, since it’s ignored on traverse step, but not to much 😃.