Isn’t this a problem with every package/library system? Is there really a solution to this that doesn’t limit packages with how they handle their dependencies?
This may also be about trust. npm probably could limit a number of dependencies that a single package can have with an arbitrary limit, but they don’t do that, because they trust the developers they won’t misuse their options. Well…
Node packaging is fucked. Node packaging remains fucked.
I am sorry, but as a noobie user of npm I don’t understand. It works pretty well for me if you use it normally for what it is supposed for.
Ouch! Thank you for noting.
And also FOSS is just cool. That’s a cherry on top.
You can download any visual studio code extension from the visual studio extensions marketplace as far as my experience goes. There’s a “download extension” link for every extension which will give you a *.vsix file. Only pity is that you won’t get any automatic updates for the extension.
8 just took a look and the VS marketplace website on my mobile and look at what I have found under the “resources” section! This is same for every extension.
Can’t Python be translated into machine code and packaged into a binary? I swear I have no experience in OS development, just curious.