ember new

[stefanpenner]

by popular request

essentially mkdir project-name && cd project-name && ember init

[knownasilya]

With all init options available?

ember new folderName [app-name] [--skip-npm-install]

Where app-name defaults to folder name, but Pascal Cased? Should --dry-run be included, doesn't seem to make sense in this context.

[stefanpenner]

ya, no dry-run

app-name dasherized as well I think

[knownasilya]

So something like: ember new folderName [--app-name] [--skip-npm-install]

[stefanpenner]

just ember new <app-name> i think the folder name being different then the app is so uncommon, people can just rename after.

[knownasilya]

I disagree, and if that was my only option, I'd do ember new App every time, and then rename the folder:

ember new App
mv App/ my-blog/

So now virtually the shortcut of the new command has become a 'longcut' 😉

[stefanpenner]

@knownasilya although that may be your path, I do not feel that is the common scenario.

I am quite nervous adding many flags and options to handle every possible permutation.

[marcioj]

@stefanpenner I guess we can close that issue

[Blackshawk]

@stefanpenner Auto-dasherizing the folder name does seem a bit odd. I ran bin/ember new TestApp today in my projects folder (which has ~ 200 folders in it). It took me a minute to realize what had happened and that the created directory was test-app.

I think dasherizing the app name in package.json, app.js, for module prefixes, etc. is great. But the root directory? My 2¢ is that it will confuse more than it helps.

[stefanpenner]

@Blackshawk ya, I agree. Will accept PR + test :)

[Blackshawk]

@stefanpenner Will oblige when I get back home. Its late. :) Good talk today, btw.

[MajorBreakfast]

I for one am not opposed to not dasherizing the folder name. Only the package name is a must. But I think you agree with me on that. Let's see what the others think.