Skip to content
This repository has been archived by the owner on Feb 5, 2022. It is now read-only.

Unable to use scoped packages from a npm or a private registry #139

Open
MDSLKTR opened this issue Nov 27, 2019 · 1 comment
Open

Unable to use scoped packages from a npm or a private registry #139

MDSLKTR opened this issue Nov 27, 2019 · 1 comment

Comments

@MDSLKTR
Copy link

MDSLKTR commented Nov 27, 2019

Hey, first of thanks for creating this! It solves almost all the use cases i have for scaffolding.

One Problem however is that i am unable to use my generator which is published in th private package registry of github requiring me to use a scoped package name. When trying to use the generator with:
sao --registry=https://npm.pkg.github.com @pixolith/sao-project-generator test

Sao will try to resolve this as a github repository. How can i circumvent this in order to use the package registry provided here? I suppose it also wouldn't work with npm scoped packages.

error Response code 404 (Not Found)
github.com/@pixolith/sao-project-generator/archive/master.zip

Thanks in advance!

@tiagoporto
Copy link

tiagoporto commented Aug 17, 2020

@MDSLKTR

You need to set npm registry global, this way npm knows where find a package

 npm config set @pixolith:registry=https://npm.pkg.github.com

This way, when npm search for scope @pixolith package, will try to find in https://npm.pkg.github.com

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

No branches or pull requests

2 participants