So npm's valuation is (presumably) based on the being the registry of record for all the things. Thus, yarn isn't a threat, so all is well…
…but I keep coming back to yarn's quiet default of yarn's fetching all packages through a proxy server it owns. What happens if it grows up?
-
-
So if yarn becomes a dominant CLI and yarn's maintainers decide to start hosting packages npm could be cut out (first slowly, then suddenly)
-
it reminds me of chrome using WebKit at the beginning, and suddenly, no more WebKit
-
I still use webkit all day every day!
End of conversation
New conversation -
-
-
npm folk are working on a registry spec, so hopefully interop will continue
-
I mean that npm's valuation story could completely evaporate, wonder the effect that sort of development would have on investment.
End of conversation
New conversation -
-
-
wait. What is yarn's proxy server you are talking about?
-
it doesn't fetch directly from npm it fetches through http://yarnpkg.org
-
thank you
-
you can always opt this out: yarn config set registry https://registry.npmjs.org/ I did that, but installation is still fast
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.