We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am testing out next-updated with angular2 which has pakcages like:
"@angular/common": "2.0.0-rc.4", "@angular/compiler": "2.0.0-rc.4", "@angular/core": "2.0.0-rc.4", "@angular/forms": "0.2.0", "@angular/http": "2.0.0-rc.4", "@angular/platform-browser": "2.0.0-rc.4", "@angular/platform-browser-dynamic": "2.0.0-rc.4", "@angular/router": "3.0.0-beta.1", "@angular/router-deprecated": "2.0.0-rc.2", "@angular/upgrade": "2.0.0-rc.4",
When funning with --available, it does not seem to see that there is a new update for all of these dependencies. (ex: 2.0.0-rc.5)
running npm outdated does see that the packages are out of date and could be updated.
npm outdated
Is this a known issue with scoped packages?
The text was updated successfully, but these errors were encountered:
Probably not supported at all, will check.
Sorry, something went wrong.
chore(test): testing using mocha scoped package names for #87
c937385
8093901
No branches or pull requests
I am testing out next-updated with angular2 which has pakcages like:
When funning with --available, it does not seem to see that there is a new update for all of these dependencies. (ex: 2.0.0-rc.5)
running
npm outdated
does see that the packages are out of date and could be updated.Is this a known issue with scoped packages?
The text was updated successfully, but these errors were encountered: