-
Notifications
You must be signed in to change notification settings - Fork 66
Default init path to CWD (like NPM init) #26
Comments
I'm not a huge fan of this - as it could clobber your working directory. |
Still I think since these apps are NodeJS and even more because the command is "init" (not "create") it makes sense to follow existing patterns in that ecosystem. But if we don't, then at least the command should fail right away IMHO since with this much output before the error, it's easy to miss - in particular in a B/W console. |
I am really uncomfortable with the level of setup we do (creating files, folders, etc.) without an explicit location argument. Maybe we don't print help right away but suggest it? Definitely cluttered as is and hides the error message. |
Let's clean it up then, since in particular the last line of help is confusing if it's printed just before the error. You could think it actually did finish:
I'd prefer:
|
Closing for #30. |
Currently if you leave out the path it neither refuses to run nor complete successfully. It should do either, and my suggestion is to default to the current working directory, like
npm init
does.The text was updated successfully, but these errors were encountered: