Private npm Modules

Hi there,

I'm wondering if there is a way of getting private npm modules into ProGet.

https://docs.npmjs.com/private-modules/intro

Thanks,

Dan

Product: ProGet
Version: 4.5.1

These are also known as "scoped packages". ProGet supports scoped packages, and many users rely on them, but we do not have a specific tutorial on using them.

If you do end up using PRoget for this purpose, we would greatly appreciate if you could share tips/tricks so other users in the community can benefit :)

Thanks for the quick response!

Scoped packages and private modules are actually two separate concepts.

I see it says in the documentation, "All private packages are scoped", but I'm interested specifically in whether ProGet can interact with private modules.

Usually if you want to install a private module via the npm CLI, you have to login using your npm account credentials; I'm wondering if there's a way of achieving the same thing using ProGet.

As far as the client is concerned, they are treated the same way. The only difference is the registry/server implementation; a "private" package may only be accessed by certain explicit users.

ProGet has a different security model than npmjs because it's intended to be used by a team (instead of being the community hub of FOSS packages). So, you can accomplish the same things using feed security.

I've just realised where the confusion is; it's purely down to my poor communication in the first post!

What I meant to ask was...

In ProGet, if you use registry.npmjs.org as a connector, is there a way of pulling in the private modules that are hosted on registry.npmjs.org?

Unfortunately the npmjs registry does not include scoped/private modules in its search index, which is the only mechanism we know of to populate a list of available modules. You can, however, navigate directly to the URL in ProGet of a modules hosted through a connector and then pull it to your local repository.

You can see the same behavior if you try to search for scoped modules on npmjs's website or with the npm client.

Is this helpful?

Thanks for your response.

I have tried navigating to the url directly and it says "Package not found". However, I can navigate to public scoped packages directly.

I have to stress that the terms "scoped package" and "private module" are not interchangeable! Scoped packages on npm can be either public or private. I am interested specifically in accessing the private ones.

I see; have you've tried putting in your npmjs username and password in the connector?

If that doesn't work, then it's not a supported scenario.