Run results for: lodash for-in vs native for-in (lodash version: 4.17.10)

Run details:

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36

Browser: Chrome 102

Operating system: Mac OS X 10.15.7

Device Platform: Desktop

Date tested: 2 years ago

HTML Preparation code:

<script src='https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.10/lodash.min.js'></script>

Script Preparation code:

var obj = Array.from({ length: 100000 }).map((value, i) => i).reduce((val, v) => { val[v] = v; return val; }, {})

Tests:

Native for-in
for (const prop in obj) { if (obj.hasOwnProperty(prop)) { const v = obj[prop]; } }
lodash for-in
_.forIn(obj, function(prop){if (obj.hasOwnProperty(prop)) { const v = obj[prop]; } })
Native for-in 2
for (const prop in obj) { if (obj.hasOwnProperty(prop)) { const v = obj[prop]; } }
lodash for-in 2
_.forIn(obj, function(prop){if (obj.hasOwnProperty(prop)) { const v = obj[prop]; } })