jlegrone / create-semantic-module

Initialize a project with conventional commits, commitizen, and commit linting

Create Semantic Module

create-semantic-module makes it easy to start using conventional commits in new or existing projects.

Adding conventional commits to your development workflow can be a big change when you work on a project with multiple contributors.

Tools like commitizen and commitlint do a great job of easing this transition, but configuring them to work together requires some boilerplate. That's where create-semantic-module comes in!

Usage

Generate a new project:

yarn create semantic-module my-module-name

Or run from within an existing project:

cd ./my-module-name
yarn create semantic-module

If using npm 5.2.0 or later, you can also use npx:

npx create-semantic-module my-module-name

License

MIT © Jacob LeGrone

create-semantic-module's Issues

Support passing CLI flags on to yeoman from create-semantic-module

create-semantic-module should support the same arguments as yo semantic-module.

An in-range update of es6-promisify is breaking the build 🚨

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency es6-promisify was updated from 6.1.0 to 6.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

es6-promisify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ codecov/project: 92.85% (+-3.58%) compared to 9cd3f11 (Details).
• ✅ codecov/patch: Coverage not affected when comparing 9cd3f11...2aa324d (Details).

---

Commits

The new version differs by 9 commits.

• ff2a343 6.1.1
• 594a4b1 fix: Give examples in async/await instead of Promise chains
• 50c9a9f fix: Rework package. scripts
• cbd4808 fix: Pin eslint to v5
• f86ebcb fix: Should test on node >= 6
• ebca605 feat: Explicitly enumerate required support in babel
• d891d6f fix: Update lint config and prettier
• 6c33205 fix: Clean up nyc config file
• 5b5a13e feat: Update supported node list

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Add prompt to configure commit linting in CI

Travis would likely be the only option for now. See https://www.npmjs.com/package/@commitlint/travis-cli

Set `packager` automatically in existing projects

• If package-lock.json or shrinkwrap.json exists, set packager to npm

• If yarn.lock exists, set packager to yarn

• Else, prompt for packager

If you want to get extra smart, never prompt for packager unless yarn is in the user's path.

Migrate to new husky config

https://github.com/typicode/husky#upgrading-from-014

An in-range update of yeoman-environment is breaking the build 🚨

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The dependency yeoman-environment was updated from 2.8.1 to 2.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

yeoman-environment is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ codecov/project: 92.85% (+-3.58%) compared to 9cd3f11 (Details).
• ✅ codecov/patch: Coverage not affected when comparing 9cd3f11...2e0660b (Details).

---

Release Notes for Release v2.9.0

• Support dependency-less generators. (#193)
• Implement custom console/streams (#190)
• Environment#run() returns a promise, unless with help option.
• Reimplement promise returned by Environment#run().
• Support for prompt with prefilled answers.
• Implement Environment#getVersion for api/feature check.
• Create a shared mem-fs-editor, so it can be removed from generator dependency.
• Lookup for ts generators.
• Update dependencies.
• Fix security warnings.
• Some experimental features.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of codecov is breaking the build 🚨

---

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

---

The devDependency codecov was updated from 3.6.5 to 3.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ codecov/project: 92.85% (+-3.58%) compared to 9cd3f11 (Details).
• ✅ codecov/patch: Coverage not affected when comparing 9cd3f11...7a2fa1e (Details).

---

Commits

The new version differs by 11 commits.

• 54d6e92 lcov.info file have been removed
• eae03d5 .borwerrc file has been removed
• 2f35de8 Version 3.7
• 0d7b9b0 Remove 'x-amz-acl': 'public-read' header (#178)
• eeff4e1 Bump acorn from 5.7.3 to 5.7.4 (#174)
• eb8a527 Merge pull request #172 from RoboCafaz/bugfix/codebuild-pr-parser
• 55d69cd Merge pull request #159 from SaferNodeJS/master
• ef348ec Verify source version before parsing PR
• e138efe Merge lastest changes
• 36bbef4 Merge branch 'master' of https://github.com/codecov/codecov-node
• 5885958 Fixing windows test and security

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of lerna is breaking the build 🚨

---

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

---

The devDependency lerna was updated from 3.20.2 to 3.21.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lerna is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ codecov/project: 92.85% (+-3.58%) compared to 9cd3f11 (Details).
• ✅ codecov/patch: Coverage not affected when comparing 9cd3f11...b3a3068 (Details).

---

Release Notes for v3.21.0

3.21.0 (2020-05-13)

Bug Fixes

• publish: Canary releases without previous tags should not explode (c9eb590)

Features

• project: Add getPackagesSync() export (068bdd7)
• version: Ignore private packages completely with --no-private (a9b9f97)

Commits

The new version differs by 16 commits.

• 3367257 chore(release): v3.21.0
• a49d674 chore: npm audit did something? ugh minimist
• 28e9941 chore: resolve kind-of 'vulnerability'
• f280286 chore: resolve acorn 'vulnerability'
• 068bdd7 feat(project): Add getPackagesSync() export
• 1713635 refactor(project): Inline array flattener
• e74a080 refactor(project): Don't mutate packageConfigs parameter
• 6e3c864 refactor(project): Extract glob option logic into helper
• f4e1a78 refactor(project): Internal default export -> named
• 164cfaa refactor(version): Use Package#set() method to assign package version
• 8dc2911 refactor(version): Avoid destructuring during graph node iteration
• a9b9f97 feat(version): Ignore private packages completely with --no-private
• 4691b93 refactor(publish): Avoid destructuring during graph node iteration
• ee2fd0e refactor(publish): Eagerly filter private packages to avoid redundant operations
• 7d36129 refactor(publish): DRY makeVersion() fallback

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Support < node 8, remove async from releases

When running this on node 6 I get Unexpected identified async prompting(). Consider making this compatible with versions of node that do not have async in core. Possibly maintain a source and build to es5 before release?