Should famous create also npm install?

[michaelobriena]

I would argue that famous create should also install the dependencies.

Running one command and being able to run the project is a better user experience that having to create, install, run.

Thoughts?

[talves]

famous create-run or famous create --run
I want the option to just install a quick seed and not deal with waiting for all the installs and spawning a serve.

[wgester]

Current thinking: leave init as is (currently aliased as create) and make create install dependencies and deploy as a single step. Possible options to start the dev server

[bdeanindy]

Might want to make the following a separate issue (but it seemed related to this issue)...

While executing famous dev in a newly created app: A suggestion for change on this page (http://famous.org/get-started.html), Step 2: famous create [name-of-project] && cd $_ && npm install

On step 3: The CLI has been built intelligently enough to be aware if dependencies are not available, but then executes npm install on behalf of the coder.

Making the initial steps for developers more transparent in the docs on Getting Started might create a better adoption experience while removing the need to incorporate commonly used and generally well understood commands.