3 ms·
>The users were asking the maintainer to re-publish a non-broken tarball. Yes, with such helpful suggestions as changing to a fresh directory because the origi
by edmccard 9y ago
>The users were asking the maintainer to re-publish a non-broken tarball.
Yes, with such helpful suggestions as changing to a fresh directory because the original directory was "corrupt". Except that wouldn't have fixed it; the problem was eventually discovered to be a bug in npm on Windows[1], so every single "republished" package would have also been broken.
[1]https://github.com/npm/npm/issues/16734 https://github.com/npm/npm/issues/16734
- justinsaccount 9y agoAnd the maintainers have not re-published a fixed tarball yet and the issue remains closed. Even after the underlying issue has been fixed in npm. I think it's pretty clear which side here is acting inappropriately.