trying to generate directive throws unknown blueprint

[zackarychapple]

Installed angular-cli today and it is throwing issues

ng g directive my-new-directive
version: 1.13.13
Could not find watchman, falling back to NodeWatcher for file system events.
Visit http://www.ember-cli.com/user-guide/#watchman for more info.
Unknown blueprint: directive

I currently have the following version installed globally:

├─┬ angular-cli@0.0.20

[filipesilva]

You're absolutely right. Just tested it myself and this isn't happening on the current dev setup but is happening in the latest npm version.

Will look into it and try to get a fix soon!

[filipesilva]

@IgorMinar this should be fixed after a new version is up.

[cironunes]

Closing as it's fixed on current master

[zackarychapple]

So this is closed but a new tag was not cut so the only way to get the working version is to build it myself? Can someone cut a tag please.

[filipesilva]

A tag should be done soon, but meanwhile you can also install the latest master directly from the repo via npm install https://github.com/angular/angular-cli.git.

[angular-automatic-lock-bot]

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.}