refactor: avoid using lodash where possible

[TrySound]

Using lodash methods does not add value where native methods and
operators can be used. In this diff I avoided lodash where possible.

Also fixed a few async tests (returned promise).

[coveralls]

Coverage decreased (-0.2%) to 88.149% when pulling 67a9e5d on TrySound:avoid-lodash into 7ae82e8 on chimurai:master.

[lgtm-com]

This pull request introduces 4 alerts when merging 9b81199 into 5384dcf - view on LGTM.com

new alerts:

• 2 for Unused loop iteration variable
• 2 for Unused variable, import, function or class

[TrySound]

Friendly ping @chimurai

[chimurai]

Hi @TrySound

Thanks for the PR.
Some effort was already started in this thread. #428

Noticed some skipped tests. What is the reason for that?

[TrySound]

I wish I remember. Probably they were not stable locally even before my changes.

[TrySound]

I plan to continue the effort after merging this PR.

[ghost]

Congratulations 🎉. DeepCode analyzed your code in 5.507 seconds and we found no issues. Enjoy a moment of no bugs ☀️.

👉 View analysis in DeepCode’s Dashboard | Configure the bot

[TrySound]

Retry DeepCode

[TrySound]

Hi @@chimurai is this good to go?

[chimurai]

Hi @TrySound,

Thanks for the reminder.

Question: Why were tests changed with extra return statement:
return expect(rewriter(rewriteFn)).resolves.toBe('/123/456');

Think it looks good. (Want to do some additional manual testing)

[TrySound]

Some tests errored with unhandled rejection when I debugged code. Promise should be returned there. Nothing need to return explicitly with async await btw.

[TrySound]

Friendly ping @chimurai

[gwellner]

Friendly ping from 2021, is this still in work ?

[chimurai]

Thanks!