npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

codemetrics-cli

v1.2.0

Published

Computes complexity in TypeScript / JavaScript files.

Downloads

117

Readme

Code Metrics - CLI

Computes complexity in TypeScript / JavaScript files.

Complexity calculation

The steps of the calculation:

  • create an AST from the input source file
  • walk through each and every node of it
  • depending on the type of the node and the configuration associated with it create a new entry about the node. This entry contains everything necessary for further use (e.g. a textual representation for the node, complexity increment, child nodes etc.)
  • show the sum of complexity of child nodes for methods and the maximum of child nodes for classes

Please note that it is not a standard metric, but it is a close approximation of Cyclomatic complexity.

Please also note that it is possible to balance the complexity calculation for the project / team / personal taste by adjusting the relevant configuration entries.

For example if one prefers guard clauses, and is ok with all the branches in switch statements then the following could be applied:

// codemetrics.config.js
// @ts-check
/** @type {import("codemetrics-cli").MetricsConfiguration}*/
var config = {};
config.ReturnStatement = 0;
config.CaseClause = 0;
config.DefaultClause = 0;

module.exports = config;

Configuration

The computation can be configured by default via the codemetrics.config.js file which is looked up automatically in the current and in the parent directories or by specifying the config file (with a relative or absolute path) via the --config parameter.

The file must have a single export, the configuration itself for which typescript type definitions are also provided. (See the example above)

Parameters

  -t, --threshold <number>  Minimum complexity to be shown
  -c, --config <string>     Path to the config file
  -l, --lint                Exit with non-zero on issues
  -d  --deep                Show complexity results from top level nodes, rather than an aggregation per file
  -p, --pattern <string>    Glob pattern

You can also use codemetrics-cli --help to get the list of the possible options.

Contributions

  • Add lint option to fail output when threshold not met - by @kopach
  • Introduce deep complexity comparison (per top level function) - by @kopach