GitHub Package Registry • Hacker News Board

Re: GitHub Package Registry

#11

Post by sambroner » Fri, May 10, 2019, 8:41 PM UTC

This is going to be hard to avoid using for teams with a private git repo, especially private mono repos.

The ability to provide any one with access to the repo access to the packages created from it removes an often frustrating management step.

Re: GitHub Package Registry

#12

Post by ezekg » Fri, May 10, 2019, 8:41 PM UTC

bye bye npmjs.com?

Re: GitHub Package Registry

#13

Post by selrond » Fri, May 10, 2019, 8:43 PM UTC

This could solve the trust issues with npm - you never know, whether the package you're installing is really from the source provided on its npm page

Re: GitHub Package Registry

#14

Post by gigatexal » Fri, May 10, 2019, 8:44 PM UTC

This is pretty interesting. Github really is becoming the social network that MS never seemed to be able to create. We already use it as our portfolio of work for potential employers. We collaborate with fellow enthusiasts and maybe even make new friends. We host our websites from it. Abuse it to store binaries, too. And now, along side, source code we can use it as a CDN of sorts to serve packages, for free, sounds pretty great. All they need now is a place to get coding questions answered (a la stackoverflow) and along with Github jobs it could be really compelling.

Re: GitHub Package Registry

#15

Post by passenger » Fri, May 10, 2019, 8:44 PM UTC

So what happens when a package on npm depends on a package on Github registry or vice versa?

Re: GitHub Package Registry

#16

Post by mmcclellan » Fri, May 10, 2019, 8:46 PM UTC

Watching the live stream now (https://live-stream.github.com/). Will likely use the Docker support near immediately. Hoping Singularity will be supportable as well.

Re: GitHub Package Registry

#17

Post by sambroner » Fri, May 10, 2019, 8:46 PM UTC

gigatexal wrote: post #14

This is pretty interesting. Github really is becoming the social network that MS never seemed to be able to create. We already use it as our portfolio of work for potential employers. We collaborate with fellow enthusiasts and maybe even make new friends. We host our websites from it. Abuse it to store binaries, too. And now, along side, source code we can use it as a CDN of sorts to serve packages, for free, sounds…

Good points.

I definitely see some people (ab)using Issues as a way to ask fairly generic coding questions. It might be time they open up another avenue for questions generally.

Re: GitHub Package Registry

#18

Post by adjkant » Fri, May 10, 2019, 8:46 PM UTC

This is early and really depends on details, but this is a super exciting move and direction for Github. I'm wary of Microsoft ownership as it becomes even more of the home for code than before, but if they keep it true to its roots it could be a real positive.

Re: GitHub Package Registry

#19

Post by hn_throwaway_99 » Fri, May 10, 2019, 8:47 PM UTC

This is going to be a huge hit for things like NPM Enterprise and Artifactory. Especially useful for small/medium teams that's want to start from the get-go with an easy way to share modules that will scale as they grow.

Re: GitHub Package Registry

#20

Post by nubs » Fri, May 10, 2019, 8:49 PM UTC

ezekg wrote: post #12

bye bye npmjs.com?

I think the National Association of Pastoral Musicians will be fine. I assume you meant npmjs.com. :)