I am looking for a way to do require("mypackage/foo") but store that file in mypackage/lib/foo.js
-
-
Replying to @wycats
@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 …1 reply 0 retweets 0 likes -
Replying to @millermedeiros
@millermedeiros a solution is only “dismissed out of hand” if you’re attacking a standards body. Node’s lame excuses are Unixy!@substack2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@millermedeiros the big difference is that standards bodies have monopoly power over all the browsers while userland projects don't1 reply 0 retweets 0 likes
@substack standards bodies have no "monopoly power". They derive their power from the fact that vendors agree through them @millermedeiros
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.