Hi Jhon, welcome to the Community!
From my understanding, you're trying to install a private repository without credentials, is this correct? That won't be possible, as you'll need your credentials to authenticate and check that you have the permissions to access that repository.
If you were referring to something different, please feel free to clarify and we'll be more than happy to help.
Best regards,
Ana
Hi Ana, thanks for your response.
The context is the following:
We have two projects that are using the same components, so we decided to create a common repository to centralize those components there.
After that, we need to import that common repository as a dependency on the projects in which these components will be used. Up to here everything normal.
The problem is that to install that repository as a dependency, each developer would have to enter their credentials when running an npm install, or we would have to hardcode some specific credentials in the package.json. In addition, at the time of deployment of the project in test and/or productive environments, there are automatic tasks to run tasks such as npm install, there would also have to define some credentials.
In short, we need a way to install the repository as a dependency without having to rely on one credential per developer.
Is there any way to make this possible? A super user or something similar?
Best Regards.
Jhon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.