@kgryte/editorconfig NPM

.editorconfig

Creates a .editorconfig file.

Installation

$ npm install @kgryte/editorconfig

Usage

var cp = require( '@kgryte/editorconfig' );

cp( dest, opts )

Asynchronously create a .editorconfig file in a specified destination directory.

cp( 'path/to/a/directory', onCreate );

function onCreate( error ) {
	if ( error ) {
		throw error;
	}
	console.log( 'Success!' );
}

The function accepts the following options:

template: .editorconfig template name. Default: 'default'.

By default, a default template is used. To specify a different .editorconfig template, set the template option.

cp( 'path/to/a/directory', {
	'template': 'default'
});

cp.sync( dest, opts )

Synchronously create a .editorconfig file in a specified destination directory.

cp.sync( 'path/to/a/directory' );

The function accepts the same options as the asynchronous version.

Notes

Supported templates may be found in the `./templates` directory and are named according to the directory name.

Examples

var mkdirp = require( 'mkdirp' );
var path = require( 'path' );
var cp = require( '@kgryte/editorconfig' );

var dirpath = path.resolve( __dirname, '../build/' + new Date().getTime() );

mkdirp.sync( dirpath );
cp.sync( dirpath, {
    'template': 'default'
});

To run the example code from the top-level application directory,

$ node ./examples/index.js

CLI

Installation

To use the module as a general utility, install the module globally

$ npm install -g @kgryte/editorconfig

Usage

Usage: editorconfig [options] [destination]

Options:

  -h,    --help                Print this message.
  -V,    --version             Print the package version.
         --templates           List templates.
  -tmpl, --template name       Template name. Default: 'default'.

Examples

$ cd ~/my/project/directory
$ editorconfig
# => creates a .editorconfig file in the current working directory

To specify a destination other than the current working directory, provide a destination.

$ editorconfig ./../some/other/directory

Tests

Unit

Unit tests use the Mocha test framework with Chai assertions. To run the tests, execute the following command in the top-level application directory:

$ make test

All new feature development should have corresponding unit tests to validate correct functionality.

Test Coverage

This repository uses Istanbul as its code coverage tool. To generate a test coverage report, execute the following command in the top-level application directory: