Leave it to hipster soyboy Javascript deveopers to destroy the package ecosystem. Probably the real issue is that unless something is done to stop this now, there'll be a precedent, and the bar will then continue to be lowered a to what "cause" will trigger people into committing this kind of sabotage, until we essentially can't trust open source.
Having to install nodejs to run a browser extension sounds extremely dodgy! Normally extensions run exclusively within the browser, subject to its sandbox security model which is pretty good, but I'm guessing you had to run a nodejs process at the same time, which probably started a server the extension could then connect to in the background? May I ask which one it was?
Wow yet another reason to not use Node
Quality content. Very informative. What a shame for an opensource project. Defeating its purpose
Leave it to hipster soyboy Javascript deveopers to destroy the package ecosystem. Probably the real issue is that unless something is done to stop this now, there'll be a precedent, and the bar will then continue to be lowered a to what "cause" will trigger people into committing this kind of sabotage, until we essentially can't trust open source.
Having to install nodejs to run a browser extension sounds extremely dodgy! Normally extensions run exclusively within the browser, subject to its sandbox security model which is pretty good, but I'm guessing you had to run a nodejs process at the same time, which probably started a server the extension could then connect to in the background? May I ask which one it was?