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

@gramex/escomplexity

v0.0.3

Published

Cyclomatic complexity calculator for JavaScript projects

Downloads

5

Readme

ES Complexity

@gramex/escomplexity measures the cyclomatic complexity of your JavaScript / TypeScript code.

Usage

In a shell, run:

npx @gramex/escomplexity

To use in your JS code as an API:

import { esComplexity } from "@gramex/escomplexity";
for await (const result of esComplexity(path)) {
  // process result for each file under path
}

esComplexity() returns an async iterator that yields results for each file under path. Each result is an object with the following keys:

  • path: the path of the file relative to the path argument
  • complexity: the cyclomatic complexity of the file
  • type: this can be
    • "complexity" if the complexity is calculated
    • "estimate" if the file could not be processed, and the complexity is estimated based on lines of code
    • "total" if it's the total entry summing up all files
  • error: the error object when parsing the file. Only if type is "estimate".

Development

To run automated tests and validate the library:

npm install
npm test

To publish, run:

npm publish

Create a tests/js-<anything> folder. Add files to test there. Add a tests/js-<anything>/expected.json that has the expected output of the test. Run npm test to validate the test.