We have our own npm package and a project that uses it, I want to publish it to a tfs feed - repository and install it from there instead of from a physical file.
I published the package to the feed from my development machine,
and I changed the reference within the project that consumes it.
The whole process works fine from my machine, but when I try to consume the package on a build process in the tfs - it fails with the error :
Unable to authenticate, your authentication token seems to be invalid.
I've created .npmrc
file at the project level with the registry address, and another file with credentials on the user directory, and I did the same on the TFS machine.
What can cause the npm install (from my feed) to not work on the tfs machine?
EDIT:
When I add prefix @my to the registry at the user-level .npmrc file - like this:
@my:registry=https://my-feed-address
The error changes to: "No valid versions available for my-package"
'Registries in my .npmrc'
option and the'Registry I select here'
option, with\without selection of aService connection
which I created that connects to my feed. But, as I wrote in the previous comment, why it would work if running this command inside the tfs server in command line - it does not work? (I do not know why) I get the same error. – Pringlenpm install
command inside the tfs server in Command Line, is not it? – Pringle