JSPM – conventional-commits-parser@0.0.3

Package Exports

conventional-commits-parser
conventional-commits-parser/lib/parser
conventional-commits-parser/lib/regex

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (conventional-commits-parser) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

parse raw conventional commits

Adapted from code originally written by @ajoslin in conventional-changelog.

Conventional Commit Message Format

Each input commit message consists of a hash (optional), a header, a body (optional) and a footer (optional).

<hash>
<header>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>

The header has a special format that includes a type, a scope (optional) and a subject

<type>(<scope>): <subject>

The footer should contain any information about Breaking Changes (optional) and is also the place to reference GitHub issues that this commit Closes (optional).

<breaking change>
<BLANK LINE>
<closes>

More details

Install

$ npm install --save conventional-commits-parser

Usage

var conventionalCommitsParser = require('conventional-commits-parser');
var through = require('through2');

var rawCommits = [
  '9b1aff905b638aa274a5fc8f88662df446d374bd\n' +
  'feat(scope): broadcast $destroy event on scope destruction\n' +
  'Closes #1',
  '13f31602f396bc269076ab4d389cfd8ca94b20ba\n' +
  'feat(ng-list): Allow custom separator\n' +
  'bla bla bla\n\n' +
  'BREAKING CHANGE: some breaking change\n'
];
var stream = through();

stream.write(rawCommits[0]);
stream.write(rawCommits[1]);

stream
  .pipe(conventionalCommitsParser())
  .pipe(through.obj(function(chunk, enc, cb) {
    console.log(chunk);
    cb();
  }));

/*=> { hash: '9b1aff905b638aa274a5fc8f88662df446d374bd',
  header: 'feat(scope): broadcast $destroy event on scope destruction',
  body: '',
  footer: 'Closes #1',
  breaks: {},
  closes: [ 1 ],
  type: 'feat',
  scope: 'scope',
  subject: 'broadcast $destroy event on scope destruction' }
{ hash: '13f31602f396bc269076ab4d389cfd8ca94b20ba',
  header: 'feat(ng-list): Allow custom separator',
  body: 'bla bla bla',
  footer: 'BREAKING CHANGE: some breaking change',
  breaks: { 'BREAKING CHANGE': 'some breaking change' },
  closes: [],
  type: 'feat',
  scope: 'ng-list',
  subject: 'Allow custom separator' }
*/

API

conventionalCommitsParser([options])

Returns an object stream.

options

Type: object

maxSubjectLength

Type: number Default: 80

The maximum subject length.

headerPattern

Type: regex Default: /^(\w*)(?:$([\w\$\.\-\* ]*)$)?\: (.*)$/

Used to match header pattern. The first capturing group captures type, second captures scope and third captures subject

closeKeywords

Type: array or string Default: [ 'close', 'closes', 'closed', 'fix', 'fixes', 'fixed', 'resolve', 'resolves', 'resolved' ]

This value is case insensitive.

Keywords that used to close issues.

breakKeywords

Type: array or string Default: ['BREAKING CHANGE']

Keywords for breaking changes.

CLI

You can use cli to practice writing commit messages or test from a file.

$ npm install --global conventional-commits-parser

$ conventional-commits-parser --help

If you run conventional-commits-parser without any arguments

$ conventional-commits-parser

You will enter an interactive shell. To show your parsed result enter "return" three times.

> fix(title): a title is fixed



result: {"hash":null,"header":"fix(title): a title is fixed","body":"","footer":"","breaks":{},"closes":[],"type":"fix","scope":"title","subject":"a title is fixed"}

You can also use cli to test commits from a file.

If you have log.txt

9b1aff905b638aa274a5fc8f88662df446d374bd

feat(ngMessages): provide support for dynamic message resolution

Prior to this fix it was impossible to apply a binding to a the ngMessage directive to represent the name of the error.

BREAKING CHANGE: The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive.

Closes #10036
Closes #9338

And you run

conventional-commits-parser log.txt

An array of json will be printed to stdout.

[
{"hash":"9b1aff905b638aa274a5fc8f88662df446d374bd","header":"feat(ngMessages): provide support for dynamic message resolution","body":"Prior to this fix it was impossible to apply a binding to a the ngMessage directive to represent the name of the error.","footer":"BREAKING CHANGE: The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive.\nCloses #10036\nCloses #9338","breaks":{"BREAKING CHANGE":"The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive."},"closes":[10036,9338],"type":"feat","scope":"ngMessages","subject":"provide support for dynamic message resolution"}
]

conventional-commits-parser