I am looking for a way to do require("mypackage/foo") but store that file in mypackage/lib/foo.js
@substack can you explain why it was a huge mistake? what huge problems did it cause?
-
-
@wycats nobody knew how it worked, the symlinks weren't portable, and it made everything really complicated https://groups.google.com/forum/?fromgroups=#!searchin/npm-/modules$20package.json/npm-/hAoPAPz4J1k/PyGdLOc0tWEJ … -
-
@millermedeiros a solution is only “dismissed out of hand” if you’re attacking a standards body. Node’s lame excuses are Unixy!@substack -
@wycats@millermedeiros the big difference is that standards bodies have monopoly power over all the browsers while userland projects don't -
@substack standards bodies have no "monopoly power". They derive their power from the fact that vendors agree through them@millermedeiros
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.