💡use macros in JavaScript (...)

[brodycj]

Coming from this PR: apache/cordova-lib#871

I noticed a case of code that was expanded when migrating from underscore to more modern JavaScript, suspect this would happen in other places.

Adding more small utility functions, and publishing some on npm for reuse would be one solution. I think this would add non-zero overhead with most if not all JavaScript interpreters.

I think using macros would further improve this situation. I found some interesting resources:

• https://github.com/kentcdodds/babel-plugin-macros - highly recommended
• https://dev.to/jakerunzer/babel-macros-2k2c
• https://lihautan.com/babel-macros/
• https://duckduckgo.com/?q=sweet.js+babel&t=h_&ia=web
• https://medium.com/@disnet/announcing-sweet-js-1-0-e7f4f3e15594
• https://duckduckgo.com/?q=babel+javascript+macros&t=h_&ia=web
• https://www.sweetjs.org
• https://archive.jlongster.com/Stop-Writing-JavaScript-Compilers--Make-Macros-Instead