Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Angular ng serve does't work after migrate to 14.2.2

See original GitHub issue

Current Behavior

Angular ng serve does’t work after migrate to 14.2.2

Expected Behavior

Angular ng serve build and run application

Steps to Reproduce

ng serve

Failure Logs

Environment

NX Report complete - copy this into the issue template

Node : 16.13.2 OS : linux x64 yarn : 1.22.17

nx : 14.2.2 @nrwl/angular : 14.2.2 @nrwl/cypress : 14.2.2 @nrwl/detox : Not Found @nrwl/devkit : 14.2.2 @nrwl/eslint-plugin-nx : 14.2.2 @nrwl/express : Not Found @nrwl/jest : 14.2.2 @nrwl/js : Not Found @nrwl/linter : 14.2.2 @nrwl/nest : Not Found @nrwl/next : Not Found @nrwl/node : Not Found @nrwl/nx-cloud : Not Found @nrwl/nx-plugin : Not Found @nrwl/react : Not Found @nrwl/react-native : Not Found @nrwl/schematics : Not Found @nrwl/storybook : 14.2.2 @nrwl/web : Not Found @nrwl/workspace : 14.2.2 typescript : 4.7.3

Community plugins: @fortawesome/angular-fontawesome: 0.10.2 @ngneat/transloco: 4.0.0 ng2-charts: 3.0.11 @compodoc/compodoc: 1.1.19 @cypress/schematic: 1.7.0 @ngneat/spectator: 10.0.1

Issue Analytics

State:
Created a year ago
Reactions:2
Comments:24 (14 by maintainers)

Top GitHub Comments

3reactions

Olstercommented, Jun 9, 2022

Yes @leosvelperez , my @angular/cli version is set to 14.0.1 at package.json and re-run npm install, but it does not works 😦

I had the same issue because of @angular-builders/custom-webpack which isn’t updated for Angular 14 as of yet. Custom-webpack has a dependency to @angular-devkit/architect v0.1302.2 and nx uses @angular-devkit/architect v:0.1400.1 to run non-nx commands (please correct me if I’m wrong here, I took a 5 minute look into the code).

After removing @angular-builders/custom-webpack I don’t get “This version of CLI is only compatible with Angular versions ^13.0.0” error anymore.

I checked the version of @angular-devkit/architect with yarn why @angular-devkit/architect

1reaction

leosvelperezcommented, Jun 14, 2022

Oh, I see, that explains why I couldn’t reproduce it, you have already fixed it. Some things might have been lost between migrations. The v1 angular.json is expected, we don’t automatically migrate that just yet. So that’s a difference to expect and it shouldn’t cause any issues.

I’m glad you were able to solve the issue.

Top Results From Across the Web

'ng serve' does not work after a double install - Stack Overflow

This works for me. npm uninstall -g angular-cli npm install --cache/tmp/empty-cache ng serve ... Just add sudo before your ng serve command. For...

ng update - Angular

Shows a help message for this command in the console. Only perform a migration, do not update the installed version.

Update Angular to v15

This topic provides information about updating your Angular applications to Angular version 15. For a summary of this information and the step-by-step ...

Angular Update Guide

Update to the new version ... Review these changes and perform the actions to update your application. Make sure you are using Node...

Upgrading from AngularJS to Angular

Applications built with component directives are much easier to migrate to ... If you start the project HTTP server with npm start ,...