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.
AFAIK Opera has some kind of patent for this, so other browsers cannit implement it so easily.
Thank you for your explanation! From what I have read ‘#pragma once’ solves the problem with mutiple includes for most modern compilers, but it’s always better to write the import guards for better compatability?
Where possible, maintain the right-click-view-source affordance. The beauty of the early web was that it was always possible to “peek behind the curtains”.
Just make the source code availible behind a visible link (hosted on Github or another similiar platform if possible). I don’t see this being a problem by any means.
- Rule - Prefer Naked HTML
HTML? Naked?? Man, I always did 😍.
deleted by creator