Well...with that in mind. If this is something you think would be useful in
Cordova - you can go ahead and use it.
I've signed a CLA and I'm already contributing (not code, but stuff with the
APIs and so on, hopefully docs in the near future), so if the project thinks
it's useful, I can contribute it. I'd have to change the license, I simply
grabbed the MIT license because it was easy, but that's not a problem.
On 9/14/2014 9:38 PM, Michal Mocny wrote:
A different name might be better, since we may publish a cordova-create
module in the future that literally just creates an empty shell (aka what
`cordova create` does).
I think this is more like a boilerplate app (akin to what yeoman does,
perhaps). No suggestions beyond that.
Anyway, thanks for sharing!
-Michal
On Sun, Sep 14, 2014 at 10:00 AM, John M. Wargo <[email protected]> wrote:
I recently created a node module called Cordova-create that takes care of
the typical developer new project workflow.
It makes calls to create, then adds a set of platforms and a set of
plugins to the project. I did this because I found myself performing the
same steps over and over again and wanted a simpler way to do it. I made it
configurable, so you can edit a cordova-create.json file in the home folder
to specify the platforms and plugins to add.
I published it to npm so others can use it, you can find it here:
https://www.npmjs.org/package/cordova-create.
Did I make a mistake by calling it cordova-create? I don't want to
confuse this module with the other cordova stuff, but I named it the way
that made the most sense for me. Does anyone care that I named it that way?
