The fix for your specific use case is to change your typescript dependency to a version available in the npm registry and to run npm install -legacy-peer-deps. however, it does appear we have a bug in how we handle dependencies that we've overwritten due to the -force flag causing this infinite loop. The other suggestion offered in the error message above is to use -force, which is what triggers this issue because we skip our normal dependency resolution and try to force instead of the 4.6.0 specified in the package.json. if i change the root requirement for typescript to either 4.5.5 or 4.6.2 which are published versions available in the registry, then npm i -legacy-peer-deps finishes successfully. This happens because your root package is depending on typescript at the specific version 4.6.0, which appears it was never published as only prerelease versions of 4.6.0 exist in the npm registry. Npm ERR! notarget a package version that doesn't exist. Npm ERR! notarget No matching version found for ERR! notarget In most cases you or one of your dependencies are requesting "update": "ng update -allow-dirty -force rxjs"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |