3.1.1 strangeness when installed with yarn instead of npm about tap-junit

[dhershman1]

Sorry if this was your first go to, but did you try removing your yarn lock file? I don't use yarn and I don't have my machine in front of me to test it right now. Though I will look into the weirdness that is happening because they only thing that changed was a version bump to minimist.

[jbergknoff-rival]

Yeah, these repro instructions put you in a completely blank slate with no yarn.lock.

[dhershman1]

I assumed so, I can reproduce it exactly as you portrayed, but it's hard to test fixes, I think this may be at the core a minimist problem, I'm going to attempt to switch minimist out with meow and see if that helps after I package it.

After testing to make sure if I use npm pack it still breaks of course.

[dhershman1]

Update: So of course when I install it from the tar file created by npm pack it works just fine...

[dhershman1]

I released version 3.1.2 onto npm, I ran a yarn add and it seems to be working again, do you mind trying version 3.1.2 and seeing if this fixes your issue?

[jbergknoff-rival]

Yep! 3.1.2 seems to fix it. Thanks!

[dhershman1]

Awesome! thanks!