-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
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
Angular CLI NOT found #25
Comments
Do we have any solution on this issue ?. We got similar error after upgrading from angular 11 to angular 12 . |
Did you find any solution yet? Until yesterday everything worked fine in our azure pipeline, but today we get the same error "Angular CLI not found." etc. npm install is performed before using the cli. |
I am experiencing the same thing as @Schoesswendter - our deployment suddenly started throwing this error after working fine for months. There were no obvious changes to our project which seem like they would've caused this. |
Same here. The pipeline are working and suddenly stoped. The NPM Install task is executing beforing angular CLI. And the Use NodeJs Task is with the same version that are working before (16.x) |
Same problem here |
Experiencing the same issue. Command line script will work in the meantime. |
My coworker restored the older implementation of our pipeline steps and it seems to have fixed the issue. Not sure exactly why this resolved it, but previously our "Use Node" step had been disabled. Restoring that seemed to be the key to getting it working again. Steps are: |
Hi, I've found the fix: If you inspect the code: https://github.com/alexruizprado/azure-pipelines-angular-cli-task/blob/master/Task1/Task1V1/index.ts If you install in your build agent a Node version compatible with your Angular version you should be fine. The actual problem is a bug in the error handling of this task. |
in CI error logs if you have
you need sync compatible version of ng cli and node |
Console throws error:
Angular CLI extensions uses @angular/cli package located in the node_modules folder of an Angular application.
even though a CLI package is present at the required location.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error, successful build.
Screenshots
Azure Devops Agent
Angular CLI:
Additional info:
Seems like extension expects "/" path which is incorrect on windows platforms ("\")
The text was updated successfully, but these errors were encountered: