he/him 
You know, it's interesting that npm supports installing tarballs from literally anywhere, but we all publish to the public npm registry
-
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" } }
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.
-
-
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...
-
npm needs to do what go/deno does though and provide a way to never ever update the source again. pretty awful when the code at the URL subtly changes and things break
- 7 more replies
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.