js-gardener

Gardener

Enforces highest code quality and minimizes package setup and maintenance complexity - so you can focus on writing code. Highly recommended if you are getting started with a new package and extremely useful if you are maintaining multiple packages.

What it does

• Enforces best code style practises using ESLint and YAMLlint
• Automates and assists with config generation
• Provides various integrity tests (e.g. checks for un-used dependencies)
• Enforces 100% test coverage using Istanbul
• Enables Continuous Integration using TravisCI
• Enables Continuous Delivery to NPM and GitHub using Semantic-Release
• Enables automates dependency updates using Greenkeeper.

Getting Started

Requirements

Install grunt globally with npm install -g grunt.

Preparation

• Create New Project (e.g. using Webstorm)
• Create New Repository on Github
• Run git init, git remote add origin URL, git checkout -b master
• Run npm init and fill in details

Install Gardener

$ npm install --save-dev js-gardener

Run Basic Setup

Create gruntfile.js in the root folder with the following contents

module.exports = (grunt) => {
  grunt.initConfig({
    pkg: grunt.file.readJSON('package.json'),
    gardener: {
      this: {
        options: {}
      }
    }
  });

  grunt.loadNpmTasks('js-gardener');
};

Then run

$ grunt gardener

This will generate some files and alter your existing package.json file.

Create your files in the lib folder and corresponding tests in the test folder (Chai works great), and ensure everything works fine by running npm test. Finalize your README.md and package.json and commit and push to GitHub.

Now configure your Badges.

Structure

Folders - Write your tests in the test and your code in the lib folder. Only test files of the format test_*.js are picked up.

Branches - You release branch is master. Develop against develop or feature branches. When you are ready for a release, merge your changes into master.

Badges

Badges represent external services that integrate with your repository. The Badges are auto generated, but the services need to be enabled manually. This section will instruct you on how to set up and utilize each service. When completed, verify each service by clicking the corresponding badge.

Before configuring external services, ensure npm test runs locally without errors and all changes are pushed.

Setup Badges

Note: If you username is different between github and a service, you will need to adjust the badge url.

Options

skip

Type: array
Default: []

Array of tasks to skip. Should not be necessary to use unless you really need to. Available tasks are:

• mkdir: Auto create folders
• copy: Copy template files
• gardener_package: Alter package.json
• gardener_configure: Alter other configuration files
• gardener_badges: Insert Badges
• projectUpdate: Install dependencies exactly as specified in package.json
• eslint: Ensure code is according to best eslint practises
• yamllint: Ensure yaml files are passing lint
• depused: Ensure all installed dependencies are used
• checkDependencies: Ensure dependencies are installed as specified in package.json
• mocha_istanbul: Run tests in test folder and force 100% coverage

cwd

Type: string
Default: process.cwd()

Specify the directory to run the tests against. Useful if you have multiple packages that you manage centralized from a parent folder.

Ignore Files

.coverignore

Define files which should be excluded from coverage. Always excluded files can be found here.

.eslintignore

Define files which should be excluded for eslint. Always excluded files can be found here.

.depunusedignore

Define packages that should be excluded from usage check. Useful when a false negative is detected, e.g. for plugins where usage is defined in configuration. Always excluded packages can be found here.

Sample Project

While this project utilizes itself for testing - how cool is that? - a cleaner example (without the grunt file) can be found here.

All my npm packages also utilize Gardener.

How to Contribute

When you contribute to any Gardener repositories, always run npm test locally before opening a PR.

Desired Changes

• Move all grunt tasks into separate function
• Use something more suitable than grunt
• Add more configuration options