@henrik yesterday I made some changes to what wrap-resolve
wraps, before it was wrapping some higher process, but now it really wraps the resolve
call (as I believe you expected, which makes sense), note now you get env input
instead of env node
, please let me know how that fits in your game
important to note though, now in the case of batch, you will only get 1 call to wrap-resolve
with the batch (`input` will be a collection)
Thanks again for all your help! Have deployed with the changes and the unexpected behavior is now gone 🙂
1🎉great to hear! 🙂 later I'll put the reset-env at the library, so you can use from it
3🎉This works very well, thank you. I can now add the size of the input to the logging with Honeycomb. (i.e., "it took 59ms, but on the other hand there were 2291 inputs")