Skip to content
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

Open
Won5ki opened this issue Jun 15, 2021 · 11 comments
Open

Angular CLI NOT found #25

Won5ki opened this issue Jun 15, 2021 · 11 comments

Comments

@Won5ki
Copy link

Won5ki commented Jun 15, 2021

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:

  1. Create Angular project.
  2. Install angular cli.
  3. Run task on Windows.
  4. See error.

Expected behavior
No error, successful build.

Screenshots
image
image

Azure Devops Agent

  • OS: Windows
  • Extension Version: 1.0.0

Angular CLI:

  • Version 12.0.4

Additional info:
Seems like extension expects "/" path which is incorrect on windows platforms ("\")

@sushilnyk
Copy link

Do we have any solution on this issue ?. We got similar error after upgrading from angular 11 to angular 12 .

@Schoesswendter
Copy link

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.

@kkoranda
Copy link

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.

@mpgalo
Copy link

mpgalo commented Jun 10, 2022

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)

@nmylle
Copy link

nmylle commented Jun 13, 2022

Same problem here

@tcukanoot
Copy link

Experiencing the same issue. Command line script will work in the meantime.

@kkoranda
Copy link

kkoranda commented Jun 13, 2022

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:
Use Node 16.10.0
npm install -> install -g @angular/cli@latest
npm install -> install
ng build

image

@nmylle
Copy link

nmylle commented Aug 8, 2022

After updating to angular v12, i'm getting the same error again, and the workaround doesn't work anymore.
Anybody knows how to fix this?

image

@emi662002
Copy link

Hi, I've found the fix:
The problem is that you are using a non compatible node version (see logs: the current version of Node () is not supported by Angular.

If you inspect the code: https://github.com/alexruizprado/azure-pipelines-angular-cli-task/blob/master/Task1/Task1V1/index.ts
any error thrown is being notified as "Angular CLI NOT found" (see line 28)

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.

@vaniprakash
Copy link

vaniprakash commented Jul 20, 2023

I am getting this issue in angular 15.0.5
Node 18.10.0. Please help me fixing this issue
image

@filipagh
Copy link

in CI error logs if you have

Using Angular CLI 12.2.18
exec error: Warning: The current version of Node (16.20.2) is not supported by Angular.

.
.
.
##[error]Angular CLI was not found.

you need sync compatible version of ng cli and node
https://angular.io/guide/versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants