Conversation
ah my bad, thanks for catching this and the exact line too. I did see this folder once or twice but thought that was because of all the other changes and investigations I was doing and just a temporary thing I broke -- turns out it wasn't temporary 😅
The semantics are only slightly different in that Another reason why I think it's a problem with |
There was a problem hiding this comment.
See my suggested change to the line that causes this -- that's the only one that needs fixing and it's not a forEach issue, it's because of how I rewrote it (removing the anonymous arrow function). With that fix in, there should be no other issues with any lodash replacement.
So if we can just change only that line, think this would be good to go!
Co-authored-by: Anton Gilgur <agilgur5@gmail.com>
|
Right, I committed that change directly 4310873 |
Partially undoing recent lodash change (#328),
_.each()semantics is apparently different fromArray.forEach()-- during the build it created "undefined" folder with bunch of empty files.