-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng update to v8 causes [error] Error: Job name "..getProjectMetadata" does not exist. #16902
Comments
|
In my case, the version of my Angular is still Angular 8, but somehow it still thinks that I'm using Angular 9, so the @angular-devkit/build-angular version in package.json became ^0.900.1, which seems not suitable for Angular 8. |
you can try version 0.803.8, the version before the one you post (in Angular 9) |
Same here! after and "npm audit fix" I got the same error. After a check I have seen: Downgrade to: |
had the same issue from accidentally installing latest version of custom-webpack |
I was receiving the same error. |
|
Downgrading to "@angular-devkit/build-angular": "~0.803.24", also fixed the issue for me. |
Same for me, Downgrading to "@angular-devkit/build-angular": "~0.803.24", also fixed the issue for me. |
Another +1 from me on downgrading the Also I feel a little silly admitting this, but make sure that, after you downgrade said package, you run |
|
@rineez-livares Yep, it's normal if you prefix the package version with This allows audit to update to the highest minor version it finds. What's not normal is that
Now Same goes for |
When a semantic version's major is a zero than the minor version is treated as a major and the carat ( If Executing |
"@angular-devkit/build-angular": "~0.803" - worked for me... |
For newbies (Like me): |
* Rearranging the package to make it compatible with Angular 8. * Keep this bug report close to you: angular/angular-cli#16902 * Bug fixes.
The fix suggested by Apro123 works. However as an alternative, one can directly downgrade the angular-devkit by running below npm command. npm i @angular-devkit/[email protected] |
Same here too, resolution : npm i @angular-devkit/[email protected] |
Same here! If your app was working and then one of a sudden it start crashing, it's probably because of the almighty "npm audit fix" which is supposed to save our lives. So In my case, I noticed this in my package.json So I Downgraded to: and then finally I |
After running npm audit fix, Now error "..getProjectMetadata" does not exist |
What to do in my case, where there are no @angular-devkit dependencies in package.json, but when I do
|
@jdhines That's surprising to her. I think seeing your |
Should I have had the
|
Closing as this seems to be an issue which is caused by See: #16902 (comment) |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🐞 Bug report
Command (mark with an
x
)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 runng 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/[email protected]
I expected that updating to v8 would resolve this.
The text was updated successfully, but these errors were encountered: