GithubHelp home page GithubHelp logo

prantlf / grunt-escomplex-report Goto Github PK

View Code? Open in Web Editor NEW
1.0 2.0 0.0 201 KB

Software complexity analysis for JavaScript projects.

License: MIT License

JavaScript 100.00%
grunt-task complexity maintainability cyclomatic-complexity halstead-complexity

grunt-escomplex-report's Introduction

grunt-escomplex-report

NPM version Build Status Coverage Status Dependency Status devDependency Status Built with Grunt

NPM Downloads

Software complexity analysis for JavaScript projects.

Table of Contents

Installation

You need node >= 4, npm and grunt >= 0.4.5 installed and your project build managed by a Gruntfile with the necessary modules listed in package.json. If you haven't used Grunt before, be sure to check out the [Getting Started] guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

$ npm install grunt-escomplex-report --save-dev

Configuration

Add the escomplex-report entry with the task configuration to the options of the grunt.initConfig method:

grunt.initConfig({
  'escomplex-report': {
    all: {
      src: ['../../src/**/!(*.spec)+(.js)'],
      options: {
        output: 'complexity.txt'
      }
    }
  }
});

Default options support the most usual usage scenario:

'escomplex-report': {
  options: {
    format: 'plain',
    output: null,
    onlyfailures: true,
    silent: false,
    newmi: true,
    force: false
  },
  ...
}

Task Options

force

Type: Boolean Default value: false

If set to true, it suppresses complexity failures. Instead of making the Grunt fail, the errors will be written only to the console.

format:

Type: String Default value: null

Specify the output format of the report.

output

Type: String Default value: null

Specify an output file for the report.

ignoreerrors

Type: Boolean Default value: false

Ignore parser errors.

maxfiles

Type: Number Default value: 1024

Specify the maximum number of files to have open at any point.

maxfod

Type: Number Default value: null

Specify the per-project first-order density threshold.

maxcost

Type: Number Default value: null

Specify the per-project change cost threshold.

maxsize

Type: Number Default value: null

Specify the per-project core size threshold.

minmi

Type: Number Default value: null

Specify the per-module maintainability index threshold.

maxcyc

Type: Number Default value: null

Specify the per-function cyclomatic complexity threshold.

maxcycden

Type: Number Default value: null

Specify the per-function cyclomatic complexity density threshold.

maxhd

Type: Number Default value: null

Specify the per-function Halstead difficulty threshold.

maxhv

Type: Number Default value: null

Specify the per-function Halstead volume threshold.

maxhe

Type: Number Default value: null

Specify the per-function Halstead effort threshold.

onlyfailures

Type: Boolean Default value: true

Report only modules and functions, which failed the complexity checks.

silent

Type: Boolean Default value: false

Do not write any output to the console.

logicalor

Type: Boolean Default value: false

Cisregard operator || as source of cyclomatic complexity.

switchcase

Type: Boolean Default value: false

Disregard switch statements as source of cyclomatic complexity.

forin

Type: Boolean Default value: false

Treat for...in statements as source of cyclomatic complexity.

trycatch

Type: Boolean Default value: false

Treat catch clauses as source of cyclomatic complexity.

newmi

Type: Boolean Default value: true

Use the Microsoft-variant maintainability index (scale of 0 to 100).

nocoresize

Type: Boolean Default value: false

Do not calculate core size or visibility matrix.

Task Data

src

Type: String|Array|Object Default value: []

Source files to have their complexity checked. Grunt file list specification.

Loading

Load the plugin in Gruntfile.js:

grunt.loadNpmTasks('grunt-escomplex-report');

Build

Call the escomplex-report task:

$ grunt escomplex-report

or integrate it to your build sequence in Gruntfile.js:

grunt.registerTask('default', ['escomplex-report', ...]);

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

  • 2018-05-03 v1.0.1 Supported installation if NPM proxy cache is used
  • 2018-04-27 v1.0.0 Dropped support of Node.js 4
  • 2018-01-29 v0.0.1 Initial release

License

Copyright (c) 2018-2019 Ferdinand Prantl

Licensed under the MIT license.

grunt-escomplex-report's People

Contributors

greenkeeper[bot] avatar prantlf avatar

Stargazers

 avatar

Watchers

 avatar  avatar

grunt-escomplex-report's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of semantic-release is breaking the build 🚨

Version 15.5.4 of semantic-release was just published.

Branch Build failing 🚨
Dependency [semantic-release](https://github.com/semantic-release/semantic-release)
Current Version 15.5.3
Type devDependency

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

semantic-release 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
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • βœ… coverage/coveralls First build on greenkeeper/semantic-release-15.5.4 at 78.431% Details

Release Notes v15.5.4

15.5.4 (2018-06-15)

Bug Fixes

  • use git ls-remote to verify if the remote branch is ahead (2b6378f)
Commits

The new version differs by 2 commits.

  • 2b6378f fix: use git ls-remote to verify if the remote branch is ahead
  • 24a8052 refactor: simply EGITNOPERMISSION error parameters

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 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.