Skip to content

ng generate without specified blueprint produces incorrect warning #4088

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

Closed
alexanderPastornicky opened this issue Jan 18, 2017 · 5 comments
Closed
Labels
needs: more info Reporter must clarify the issue

Comments

@alexanderPastornicky
Copy link

alexanderPastornicky commented Jan 18, 2017

OS?

Ubuntu 16.04

Versions.

angular-cli: 1.0.0-beta.25.5
node: 6.9.1

command ng generate without specified blueprint/name produces warning below

The ember generate command requires a blueprint name to be specified. For more details, use ember help.

@filipesilva
Copy link
Contributor

Are you absolutely sure you have the latest version? You can double check your local version of the CLI with npm ls angular-cli.

We fixed this in beta.25.5 so I find it weird you're still getting it:

kamik@T460p MINGW64 /D/sandbox/master-project (master)
$ ng generate
The `ng generate` command requires a blueprint name to be specified. For more details, use `ng help`.

@filipesilva
Copy link
Contributor

Oh my bad, it's actually fixed on master only via #4026 by @clydin. The fix will be out on the next release.

@hasanalbukhari
Copy link

hasanalbukhari commented Mar 8, 2017

getting this error on the following version:

ng --version
_ _ ____ _ ___
/ \ _ __ __ _ _ | | __ _ _ __ / | | | |
/ △ \ | '
\ / _ | | | | |/ _ | '
| | | | | | |
/ ___ | | | | (
| | || | | (| | | | || | | |
// __| ||_, |_,||_,|| _|||
|___/
@angular/cli: 1.0.0-rc.1
node: 6.10.0
os: darwin x64

@pipiscrew
Copy link

pipiscrew commented Mar 8, 2017

the cmd use is
ng generate component my-new-component

or whatever type you wish, more at
https://github.com/angular/angular-cli

@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
needs: more info Reporter must clarify the issue
Projects
None yet
Development

No branches or pull requests

4 participants