-
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
ng help does not work outside an CLI generated project #3989
Comments
however, I see No help entry for 'serve.run' message within the help content. other than
|
I also seem to be able to run @CarreraPHP yeah those entries in red are a bug. I'll make an issue for it. #3994 |
Could be yarn related. Does it happen if installed with npm? |
@clydin. I wanted to check out your premises. So I removed the global CLI, installed it again with NPM, and it worked. I can now confirm it does not work when installed global with yarn, but it does work when installed with NPM. (I double-checked.) Hmm, should I file an issue at yarn for this, or is it still a CLI issue? |
I think you need to set a path variable for the /bin for Yarn. I think by default it saves your dependencies somewhere else (not sure where, I had to do it a long time ago because I had a similar issue). Hope that helps. |
@ScaryWolfMan This might be the solution, but then again, I expect my package manager to handle that, as it is its job. Unless the CLI does something dirty in this regards. Then it's a CLI issue. Hence my question about where I should file the issue. |
This is most likely related to yarnpkg/yarn#648 |
Closing this as yarn only. |
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. |
OS?
Ubuntu 16.04.1 LTS
Versions.
angular-cli: 1.0.0-beta.25.5
node: 6.9.4
os: linux x64
Repro steps.
cd ~/nonCLIfolder
ng help
The log given by the failure.
Not a big issue, but if you want to get the option for
ng new
its a bit of a bummer.The text was updated successfully, but these errors were encountered: