I opened the comments just to warn people how shitty this article is, but I guess I was not the only one.
In my experience foraging is regional, locals know what kind of mushrooms grow in which forest. This kind of "look out for these LOL" list is not useful at all.
e.g in my region the parasol mushrooms are one of the best picks due to their sheer size and distinct characteristics. I would recommend it more to beginners.
Some mushrooms on the list have similar quite toxic ones, and here there is only one picture, there is no explanation on what to look out for. I hope no reader gets the false impression of it being safe (which is literally in the title of the article). Hate it.
The story is the journey, and there is no story without suspense. The URL is the dust jacket- some people are going to see the URL even before the title. No one said anything about clickbait. Any URL without the spoiler is better.
I'm interested why this is not the default behaviour. Would it break anything legit if npm would just simply switch to this behaviour? Are there any strong arguments against this?
I'm interested in use-cases where access to anything outside the current folder (the folder npm is called in) is justified and depended on.
How are packages with native dependencies build? Presumably that requires access to the compiler and libraries? (I don't know anything about npm works, so read those as real and not as rhetorical questions ;))
In my experience foraging is regional, locals know what kind of mushrooms grow in which forest. This kind of "look out for these LOL" list is not useful at all.
e.g in my region the parasol mushrooms are one of the best picks due to their sheer size and distinct characteristics. I would recommend it more to beginners.
Some mushrooms on the list have similar quite toxic ones, and here there is only one picture, there is no explanation on what to look out for. I hope no reader gets the false impression of it being safe (which is literally in the title of the article). Hate it.