Skip to content
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

Running ng help outputs: No help entry for <cmd> #3976

Closed
beeman opened this issue Jan 13, 2017 · 1 comment · Fixed by #3982
Closed

Running ng help outputs: No help entry for <cmd> #3976

beeman opened this issue Jan 13, 2017 · 1 comment · Fixed by #3982

Comments

@beeman
Copy link
Contributor

beeman commented Jan 13, 2017

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

OS X Sierra

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.25.5
node: 7.2.0
os: darwin x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

The log given by the failure.

Normally this include a stack trace and some more information.

Output contains these lines:

...
No help entry for 'build.run'
...
No help entry for 'github-pages-deploy.run'
...
No help entry for 'init.run'
...
No help entry for 'serve.run'
...

Mention any other details that might be useful.


Thanks! We'll be in touch soon.

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant