> Developers should exercise caution when typing npm commands in the terminal when especially when using flags.<p>The double ”when” is quite funny here, given the nature of npm problem described in the article.
A simple logic of NOT “-“ would have blocked any reintroduction/upgrade of unintended “-“ package, coupled with a inertiazed package replacing the accidentally-introduced “-“ package.<p>Yeah, those who depend on the original but accidental “-“ package for its functionally should suffer any consequential breakage that may have resulted from it.<p>*insert*fake*tear*here*
> A mysterious, one-letter npm package named "-" sitting on the registry since 2020 has received over 700,000 downloads.<p>...then a few lines further down the article:<p>> An npm package called "-" has scored almost 720,000 downloads since its publication on the npm registry, since early 2020.<p>Kinda frustrating that the same information is being written twice imo... And then two ads in a row follow that