question-mark
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.

ng update to v8 causes [error] Error: Job name "..getProjectMetadata" does not exist.

See original GitHub issue

🐞 Bug report

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • xi18n
  • run
  • config
  • help
  • version
  • doc

Description

A clear and concise description of the problem...

When I run ng update @angular/cli@8 @angular/core@8, I then get an error when I run ng build

[error] Error: Job name "..getProjectMetadata" does not exist.

Details are also here https://stackoverflow.com/questions/59447679/an-unhandled-exception-occurred-job-name-getprojectmetadata-does-not-exist

I resolved this by running npm i @angular-devkit/build-angular@0.803.24

I expected that updating to v8 would resolve this.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:25
  • Comments:24 (2 by maintainers)

github_iconTop GitHub Comments

85reactions
sterlpcommented, Feb 23, 2020

Same here!

after and β€œnpm audit fix” I got the same error. After a check I have seen: β€œ@angular-devkit/build-angular”: β€œ^0.900.3”,

Downgrade to: β€œ@angular-devkit/build-angular”: β€œ~0.803.24”,

23reactions
indrapalijamacommented, Feb 13, 2020

🐞 Bug report

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • xi18n
  • run
  • config
  • help
  • version
  • doc

Description

A clear and concise description of the problem… When I run ng update @angular/cli@8 @angular/core@8, I then get an error when I run ng build

[error] Error: Job name "..getProjectMetadata" does not exist.

Details are also here https://stackoverflow.com/questions/59447679/an-unhandled-exception-occurred-job-name-getprojectmetadata-does-not-exist

I resolved this by running npm i @angular-devkit/build-angular@0.803.24

I expected that updating to v8 would resolve this.

you can try version 0.803.8, the version before the one you post (in Angular 9)

Read more comments on GitHub >

github_iconTop Results From Across the Web

angular - Job name "..getProjectMetadata" does not exist
I got this error after running npm audit fix . Although I lock dependencies it still upgraded to angular 9 which I don't...
Read more >
An unhandled exception occurred Job name ...
When I start to run my Application, I get this error: **[error] Error: Job name "..getProjectMetadata" does not exist.** at Observable.
Read more >
Job name "..getProjectMetadata" does not exist. - Manar System
An unhandled exception occurred: Job name β€œ..getProjectMetadata” does not exist. It seems to be a problem with @angular-devkit/build-angular. Try updating ...
Read more >
Job name "..getProjectMetadata" does not exist-angular.js
My Jenkins build requires me to run the npm audit fix command to download dependencyes. This command makes the same error appear again....
Read more >
Data Binding Error: Package Viewcontroller Does Not Exist
Android Studio - Data Binding Error: Package Viewcontroller Does Not Exist ... ng update to v8 causes [error] Error: Job name "getProjectMetadata" does...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found