- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [x] version
- [ ] doc
root@3a48fcb74f54:/app# node --version
v10.13.0
root@3a48fcb74f54:/app# npm --version
6.4.1
root@3a48fcb74f54:/app# uname -a
Linux 3a48fcb74f54 4.9.93-linuxkit-aufs #1 SMP Wed Jun 6 16:55:56 UTC 2018 x86_64 GNU/Linux
npm install -g @angular/[email protected]
root@3a48fcb74f54:/app# npm install -g @angular/[email protected]
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @schematics/[email protected]
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of '@angular/cli'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-11-08T22_54_53_573Z-debug.log
To be installed.
It looks like the dependency: @schematics/[email protected] is not available.
Same problem here!!!
npm ERR! notarget No matching version found for @schematics/[email protected]
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of '@angular/pwa'
npm ERR! notarget
If you are using a proxy or cache, the registry information may have not propagated fully.
Both of them are published:
https://www.npmjs.com/package/@schematics/angular
https://www.npmjs.com/package/@schematics/update
@clydin I'm not using proxy or cache, and I cannot install it, with the error as reported.
This shouldn't be closed without investigating.
@angular/cli was published 1 hour ago, but im playing with cli within 3hrs and started getting error too within 1 hour. im not using any cache/proxy, have cleared/verified npm's cache many times - still reproduced
Started working for me. This could be another of those npm issues that happen from time to time.
Yes, now working
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
_This action has been performed automatically by a bot._
Most helpful comment
@angular/cli was published 1 hour ago, but im playing with cli within 3hrs and started getting error too within 1 hour. im not using any cache/proxy, have cleared/verified npm's cache many times - still reproduced