component-create: prompt instead of error on invalid repo

[aeosynth]

would be nice if component-create immediately noticed invalid repos and responded with help text, instead of throwing an error at the end

$ component -V
0.16.3
$ component create
repo (username/project): foo
description: 
does this component have js? 
does this component have css? 
does this component have html? 

/usr/local/share/npm/lib/node_modules/component/bin/component-create:88
    if (2 != repo.length) throw new Error('repo must be <username>/<project>')
                                ^
Error: repo must be <username>/<project>
    at buf (/usr/local/share/npm/lib/node_modules/component/bin/component-create:88:33)
    at next (/usr/local/share/npm/lib/node_modules/component/node_modules/commander/lib/commander.js:828:24)
    at /usr/local/share/npm/lib/node_modules/component/node_modules/commander/lib/commander.js:831:9
    at ReadStream.<anonymous> (/usr/local/share/npm/lib/node_modules/component/node_modules/commander/lib/commander.js:764:5)
    at ReadStream.g (events.js:175:14)
    at ReadStream.EventEmitter.emit (events.js:95:17)
    at ReadStream.<anonymous> (_stream_readable.js:736:14)
    at ReadStream.EventEmitter.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:408:10)
    at emitReadable (_stream_readable.js:404:5)

[vendethiel]

agreed, this bites me some times

[micky2be]

It should be optional anyways. I mostly create local components, why should I enter a repo?

[ericgj]

@micky2be component create --local doesn't ask for a repo

[tj]

+1

[micky2be]

@ericgj My bad, I didn't know that. Very useful information.
I always create the files manually anyways, I'm using a different style guide.

[jonathanong]

componentjs/create.js#6