We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command line
v0.43.0.0
Config file not found. File name: '.npmrc' vsts-npm-auth. Below command executed:
vsts-npm-auth -config .npmrc -targetconfig c:\Users\rajib.npmrc
it always return me the error :
Config file not found. File name: '.npmrc'
.npmrc file present in c:\Users\rajib.npmrc
Before that i installed it globally:
npm install -g vsts-npm-auth --registry https://registry.npmjs.com/ --always-auth false
Please help.
dev.azure.com (formerly visualstudio.com)
No response
Windows 11
vsts-npm-auth v0.43.0.0 ----------------------- Config file not found. File name: '.npmrc'
[REPLACE THIS WITH YOUR INFORMATION]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
New issue checklist
Task name
Command line
Task version
v0.43.0.0
Issue Description
Config file not found. File name: '.npmrc' vsts-npm-auth. Below command executed:
vsts-npm-auth -config .npmrc -targetconfig c:\Users\rajib.npmrc
it always return me the error :
vsts-npm-auth v0.43.0.0
Config file not found. File name: '.npmrc'
.npmrc file present in c:\Users\rajib.npmrc
Before that i installed it globally:
npm install -g vsts-npm-auth --registry https://registry.npmjs.com/ --always-auth false
Please help.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 11
Relevant log output
vsts-npm-auth v0.43.0.0 ----------------------- Config file not found. File name: '.npmrc'
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: