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
Describe the bug Getting ERROR running scanner:run: Cannot find module '/home/vsts/.local/share/sfdx/node_modules/eslint/conf/eslint-recommended.js' in Azure DevOps pipeline.
To Reproduce Step 1 - Create node.JS build YML pipeline on Azure DevOps Step 2 - Create new job for scanning salesforce org code by running below command sfdx scanner:run --target ./changed-sources --engine "eslint-lwc,pmd" --format table
sfdx scanner:run --target ./changed-sources --engine "eslint-lwc,pmd" --format table
Expected behavior Should provide violation report like mentioned in below image.
Screenshots
Desktop (please complete the following information):
Additional context Issue is only on Azure DevOps Pipeline level not on local machine.
"Workaround": Have you found any ways to sidestep the problem? No
"Urgency": Not business-stopping.
The text was updated successfully, but these errors were encountered:
hi @sameer544 thanks for raising this. We are working on this issue - please follow #986 and I'll close this as a duplicate in the meantime
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Getting ERROR running scanner:run: Cannot find module '/home/vsts/.local/share/sfdx/node_modules/eslint/conf/eslint-recommended.js' in Azure DevOps pipeline.
To Reproduce
Step 1 - Create node.JS build YML pipeline on Azure DevOps
Step 2 - Create new job for scanning salesforce org code by running below command
sfdx scanner:run --target ./changed-sources --engine "eslint-lwc,pmd" --format table
Expected behavior
Should provide violation report like mentioned in below image.
Screenshots
Desktop (please complete the following information):
Additional context
Issue is only on Azure DevOps Pipeline level not on local machine.
"Workaround": Have you found any ways to sidestep the problem? No
"Urgency": Not business-stopping.
The text was updated successfully, but these errors were encountered: