Skip to content
This repository has been archived by the owner on Jan 11, 2019. It is now read-only.

Create a Yeoman generator #2

Open
michaelryancaputo opened this issue Mar 2, 2015 · 10 comments
Open

Create a Yeoman generator #2

michaelryancaputo opened this issue Mar 2, 2015 · 10 comments

Comments

@michaelryancaputo
Copy link

Would love to see this in a yeoman generator!

@jamesmanning
Copy link

+1 👍

@Glavin001
Copy link

+1

1 similar comment
@mmahalwy
Copy link

+1

@mmahalwy
Copy link

@RickWong I can try to help with this. I been meaning to learn Yeoman generators.

@RickWong
Copy link
Owner

Thanks! That would be great.

@natecox
Copy link

natecox commented Sep 19, 2015

+1 for this

@alexlafroscia
Copy link

@RickWong I'm taking a stab at making a Generator from this project right now. I'm pretty sure that the repo would need to change to make the structure that a Yeoman generator expects, though. Would you be interested in a PR that made that drastic of a change?

Basically, it would require two major changes:

  1. The package.json file would need to be updated to match their requirements, which is pretty much just adding generator- in front of the name and then adding a particular keyword
  2. The current root of the project would need to get moved into app/templates/ or, if you prefer the extra level of organization, into generators/app/templates/. Turns out that isn't necessary after all!

That would just be to generate this exact project using Yeoman, which would be pretty cool. There are lots of cool possibilities for new routes and stuff through Yeoman, too, if you wanted to get fancy with it 😄

@RickWong
Copy link
Owner

Hi @alexlafroscia, yes I would definitely be interested.

@alexlafroscia
Copy link

@RickWong it's possible to have the Yeoman generator in a separate repo, would you prefer that? Or adding it into this one?

@alexlafroscia
Copy link

I decided to give getting it all in one repo a shot, since that'll be simpler in the long run. You'll have to change the name of the project in the NPM registry, but that shouldn't be an issue. I think you'll probably want to have Yeoman be the default way to install the project, too, since it's a bit easier than needing to clone the repo, nuke the original .git folder and then start your new project.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants