use-init/generator-init

DEPRECATED - A Yeoman generator for INIT

generator-init's Issues

A plugin system via sub-generators

This is the bug to continue the discussion from use-init/init#67.

I wrote up an outline on how we can achieve the goal:

---

I think a decent way would be to clone the plugin to install in a directory, move all the things around and delete the rest of the repo. This would mean that we only need a convention for

1. repo URLs
2. file names
3. directories

Most of this is given:

1. Repos for files can be matched as "use-init/init-" at GitHub. We could later extend this to make it customizable and stuff.

__ 2.__ I've outlined this above: We need to copy the {taskname}.js file into the folder grunt/plugins, we need to run npm install --save-dev {pluginname} and lastly add necessary config options to main project's config.js which are stored in a plugin specific config.js file.

3. We need a temporary folder to place the repos in. I'd suggest to name it .init-cache. Everything else is stated in 2..

---

cc: @distilledhype @sergiovilar

Turn on Travis service hook

Hey @drublic or @anselmh can you turn on Travis for this repo?

Update to latest yeoman-generator

It needs to happen one day :) I guess it will be kind of a rewrite more than a quick version bump though. On the while be sure to update the init version this uses too.

cc @drublic @distilledhype It's a little sad to see this generator kind of dying. Would you be in me doing a total rewrite of it one day? Won't get to it in the upcoming weeks but would be interested in doing it one day.

Write more tests

sub-generator for INIT plugins

#1 (comment)

Write tests for sub-generator page

Write tests for sub-generator init:module and sub-generator init:jqueryplugin

@sergiovilar do you want to take this as well?

Get the templates up to date with the current version.

sub-generator for JavaScript plugins

#1 (comment)

sub-generator for HTML pages

#1 (comment)

sass-mixins not included in bower.json

If you choose SCSS as preprocessor sass-mixins isn't included in package.json.

Compass isn’t configured properly when chosen as preprocessor

Running grunt after generating init yields an error

Warning: Task "sass:dev" not found. Use --force to continue.
Aborted due to warnings.

In fact getting that error for anything related to sass
Any ideas what could be causing this?

grunt-concat-sass not included in package.json

If you choose SCSS as preprocessor grunt-concat-sass isn't included in package.json.
That's bad because you get a warning when compiling: Task "sass" not found. This might be an easy fix :) Thanks.

Make sub-generator `module` better

Awesome sub-generator for modules. There are some things we might want to update though:

• Use the generated module's name as argument in test-spec define callback
• Add test-spec in test/spec.js
• Name the suite after the module (describe('modulename', function () {}));
• Don't include any tests in test spec
• Don't add content of example module in new JS file
• Add current date and author name in header

It would be fantastic if we could include any of these. I've prioritized them from top to bottom.

Thanks so much for your work @kahlil and @sergiovilar :)

sub-generator for JavaScript modules

#1 (comment)

• Add test file scaffolding per AMD module.

Ask which server config to use

The generator should ask which server config (apache / nginx) to use in the setup wizard.

Initial alpha release

@drublic @anselmh

The first alpha of the generator is on npm.

To check it out do:

npm install -g yo
npm install -g generator-init
yo init

For now it asks you a bunch of stuff and then just copies files and fills in your name and project name where it makes sense.

Just put in bugs and feature request in the issues here so we can discuss them and work them off.

Update the generator to prepare for upcoming versions

A list of changes that need to be done can be found in this blog post: http://yeoman.io/blog/cleanup.html