-
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
the cli should check npm "dependencies" for the version #5112
Comments
delasteve
added a commit
to delasteve/angular-cli
that referenced
this issue
Mar 18, 2017
…d in devDependencies fixes angular#5112
delasteve
added a commit
to delasteve/angular-cli
that referenced
this issue
Mar 18, 2017
… in devDependencies fixes angular#5112
delasteve
added a commit
to delasteve/angular-cli
that referenced
this issue
Mar 19, 2017
… in devDependencies fixes angular#5112
delasteve
added a commit
to delasteve/angular-cli
that referenced
this issue
Mar 19, 2017
… in devDependencies fixes angular#5112
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I just updated a project to rc.0 but I still got the warning saying that I should update it. This is because in my project the cli is added as a dependency and not a devDependency... Changing that gets rid of the warning.
I think that it should check both for the cli version, not just devDependency.
OS?
Windows 10
Versions.
1.0.0-rc.0
Repro steps.
Add the cli as a dependency in package.json instead of devDependency
The log given by the failure.
The text was updated successfully, but these errors were encountered: