ideas

[doowb]

I was going to suggest adding some of these to verb, but I think they belong in generate (as generate plugins)

• generate-browserify: adds npm run browserify to package.json with default (or custom) browserify command
• generate-coveralls: adds npm run coveralls to package.json with default (or custom) coveralls command
• generate-mocha: adds npm test to package.json with default (or custom) mocha command, creates test folder with test.js file. optionally pass additional arg to create a named test/{name}.js test file.

Just some ideas on standalone plugins that don't create entire projects, but just modify existing functionality to add these things faster.

[tunnckoCore]

generate-banner: generating header banners with copyright and etc

[jonschlinkert]

I have that somewhere, and updater-banner. (I know, updater-* sounds weird, but there were too many update-* libs already published)

[jonschlinkert]

want to create an issue/request for the ones you need? I'll let you know which ones we have and I can prioritize pushing them up, or anyone is free and encouraged to create generators

edit: if the issues are separate I'm more likely to remember

[tunnckoCore]

edit: if the issues are separate I'm more likely to remember

yea, okey, i'll keep that in mind

want to create an issue/request for the ones you need

not so much. i mostly will just override the templates of already existing, i'm playing now.

[tunnckoCore]

• generate-repo - creates github repo, init in dir; (and first commit? task for that?)
  • use github-base
• generate-nyc - should play with generate-coveralls and generate-travis
  • adds nyc to decDeps
  • adds coverage script "nyc report --reporter=text-lcov | coveralls" maybe without coveralls?
  • adds after_success: npm run coverage to .travis.yml
  • ref https://github.com/istanbuljs/nyc
• generate-standard-version - adds standard-version to devDeps
  • and scripts.release: standard-version
  • ref https://github.com/conventional-changelog/standard-version
• generate-pre-commit adds pre-commit to devDeps
  • ref: https://github.com/observing/pre-commit
  • adds "precommit.silent": true to package.json (that's enoughbecause it will exit with 1, you dont need to know anything else)?
  • maybe prompt to ask if you wanna more scripts to be run instead of just test? if not given, adds just precommit.silent: true
  • otherwise precommit.run: "task1, task2, task3" and precommit.silent: true - run also accepts array of strings
• generate-standard-style adds standard to devDeps
  • adds scripts.lint: standard --verbose (verbose because shows eslint rules)
  • adds scripts.pretest: npm run lint
• generate-commitizen or generate-commitizen-default? ref: https://github.com/commitizen/cz-cli
  • runs commitizen init cz-conventional-changelog --save-dev
• generate-keywords prompts for keywords
• generate-lazy-cache
• generate-files add files to files field
• generate-standard-readme ref https://github.com/RichardLitt/generator-standard-readme
• generate-pre-commit-hook boilerplate for creating pre-commit compatible hooks
  • because ajoslin/angular-precommit sucks
  • cool: https://github.com/paradox41/validate-commit

ref: https://github.com/kentcdodds/validate-commit-msg
ref: https://github.com/gtramontina/ghooks
ref: https://github.com/Frikki/validate-commit-message
ref: https://github.com/nkzawa/git-scripts

[tunnckoCore]

• generate-contributors
  • use github-contributors?
  • ref: https://github.com/kentcdodds/all-contributors ?
  • one implementation: https://github.com/jfmengels/all-contributors-cli
  • https://github.com/jfmengels/all-contributors-cli/blob/master/.all-contributorsrc

[jonschlinkert]

creates github repo, init in dir; (and first commit? task for that?)

is generate-git similar to what you mean?

I have update-keywords, I can push that up soon. we might be able to combine logic for those

[tunnckoCore]

Actually, partially, yea. I just forgot it. But with creates github repo I meant creating it in github, not only locally - and i imagine that it should respect/get/use gen dest or project name.

[jonschlinkert]

respect/get/use gen dest

or just --cwd. that's what I usually use

[dawsbot]

Is there already a utility to update a pre-existing package.json? That'll certainly be needed in the proposed generate-nyc.

I've been working on a sort of jscodeshift but for json files. Mostly a one-night experiment since I assumed a json mutation helper already exists. Are y'all aware of one? If not, I'll polish it up and publish it so we can use that to more easily update package.json's.

[jonschlinkert]

Is there already a utility to update a pre-existing package.json? That'll certainly be needed in the proposed generate-nyc.

here are couple, I'm not sure if they do what you need.

• https://github.com/jonschlinkert/normalize-pkg: this can be customized pretty easily with a schema
• https://github.com/jonschlinkert/gulp-normalize-pkg

fwiw, I created "updater-package" for update but I haven't pushed it up yet. It's pretty opinionated atm - mostly because I wasn't sure what I wanted it to do yet lol. but all of these tools are made to be configurable, and we can change defaults.

I can push up updater-package just so you can see what I mean. If you find generate useful, Update goes really well with it. Every time I run a generator to create a new project, the first thing I do is run update and it changes all the files to be the way I like them. which is great since it doesn't matter what conventions are used in the generator...

the tool you mentioned for json files sounds really interesting

[tunnckoCore]

@dawsonbotsford, i'm workin on @postjson, and it may help in future.

[tunnckoCore]

• generate-choo - ref https://github.com/yoshuawuyts/choo

edit: updated above lists to be task/todo lists