Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

Support for @scoped packages #138

Open
mikerandall opened this issue Mar 24, 2016 · 5 comments
Open

Support for @scoped packages #138

mikerandall opened this issue Mar 24, 2016 · 5 comments
Assignees
Milestone

Comments

@mikerandall
Copy link

Description

Need the ability to sign in and retrieve privately scoped NPM modules. A username and password field on the package would work, but it might be nice to use an .npmrc file that would be placed in the image.

@grafjo
Copy link
Contributor

grafjo commented Mar 24, 2016

@mikerandall have you tried ~/.npmrc?

@mikerandall
Copy link
Author

Yes, but that isn't the problem. There's no way to download scoped packages, and no way to sign in as a user with the current configuration. As more people stop using Bower, scoped packages are going to become more popular.

@Ma27
Copy link
Collaborator

Ma27 commented Mar 25, 2016

According to the docs (https://docs.npmjs.com/misc/scope) it should be possible to do this with some npm commands. It should be possible to do this with the usage of "exec", but actually you're right, such a feature should exist in 2.0 :)

Am 24.03.2016 um 22:46 schrieb Mike Randall [email protected]:

Yes, but that isn't the problem. There's no way to download scoped packages, and no way to sign in as a user with the current configuration. As more people stop using Bower, scoped packages are going to become more popular.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

@Ma27 Ma27 self-assigned this Mar 25, 2016
@Ma27 Ma27 added this to the 2.0 milestone Mar 25, 2016
@Ma27 Ma27 modified the milestones: 2.1, 2.0 Mar 24, 2017
@Ma27
Copy link
Collaborator

Ma27 commented Mar 24, 2017

postponing to 2.1: 2.0 contains some important releases and it would be nice to get a release in the next time

@Ma27
Copy link
Collaborator

Ma27 commented Apr 14, 2018

@mikerandall just so you know - I still know about this feature request, I'm unfortunately way to busy with different things, so I'm currently unable to do active feature development for puppet-nodejs (sorry about that!) I don't know if you're still in need for this, but I don't think that I'll be able to do this in near time :(

It would be totally awesome if you could file a patch, but no rush, we'll see if I have time for this in the future :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants