Hey, thanks for the feedback!
Indeed, I’m not assuming that’s a direct vvvv issue since the error clearly emanates from a nuget setup, but I assumed something was off in the way vvvv handles that, hence the report :-)
I’ll try the workaround you suggested and report in this post, thanks!