Job name “..getProjectMetadata” does not exist

Source: https://stackoverflow.com/questions/59447679/an-unhandled-exception-occurred-job-name-getprojectmetadata-does-not-exist

I had this error after npm audit found vulnerabilities in the version of @angular-devkit/build-angular that I was using. I ran npm audit fix which updated it to 0.900.2, but when I ran ng serve it gave the error quoted in the question.
I resolved it by downgrading to version 0.803.25. This was the highest version I could find which did not cause any errors when running ng serve. The vulnerabilities found by npm audit are resolved in this version.
This is the command I ran:
npm i @angular-devkit/build-angular@0.803.25
-
Nhãn: ,

Không có nhận xét nào:

Đăng nhận xét

Đăng ký: Đăng Nhận xét (Atom)

Cold Turkey Blocker

 https://superuser.com/questions/1366153/how-to-get-rid-of-cold-turkey-website-blocker-get-around-the-block Very old question, but still wan...

  • poetry shell
      Basic usage | Documentation | Poetry - Python dependency management and packaging made easy (python-poetry.org) Activating the virtual env...
  • Modify File Permissions with chmod
      Modify File Permissions with chmod | Linode Modify File Permissions with chmod The chmod command allows users to change read and write per...
  • Python: poetry create poetry.lock from pyproject.toml
    Basic usage | Documentation | Poetry - Python dependency management and packaging made easy (python-poetry.org)   Python: poetry create poet...