You know, it's interesting that npm supports installing tarballs from literally anywhere, but we all publish to the public npm registry
-
-
Replying to @mjackson
You can even specify the tarball checksum if you append
#HASH_HERE to the end of the URL! Yarn and npm should also handle caching it in the same way as a regular registry tarball.3 replies 0 retweets 16 likes -
Replying to @sebmck
Agree. It's like the killer feature of package.json that goes completely ignored. Wonder why. There's even a shorthand if you host your packages on GitHub! You can do: { "dependencies": { "react-router": "ReactTraining/react-router#v4" } }
3 replies 1 retweet 13 likes -
Replying to @mjackson
There's actually a ton of shorthands that you may not know about! You can use gitlab:, bitbucket:, gist: https://github.com/npm/hosted-git-info … All supported in Yarn too.
1 reply 4 retweets 23 likes -
Replying to @sebmck
Holy crap ... gist??!! So, like, nobody ever actually has to use the public npm registry if they don't want to. My mind is moving at a million miles a second right now...
4 replies 0 retweets 26 likes
Yep, a gist is actually just a git repo that you can clone, which makes the support super easy https://help.github.com/articles/forking-and-cloning-gists/#cloning-gists …
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.
he/him 