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

code-metrics-module

v1.0.1

Published

A module for calculating code metrics

Downloads

9

Readme

code-metrics-module

npm version License

A code metrics library for analyzing the complexity and statistics of code files in various programming languages.

Installation

npm install code-metrics-module

Usage

const calculateCodeMetrics = require('code-metrics');

const filePath = 'path/to/your/code/file';
const metrics = calculateCodeMetrics(filePath);

console.log(metrics);

| Language | Tested | | --------- | ----------- | | JavaScript| ✅ Fully tested | | PHP|❌ Not fully tested| | Java|❌ Not fully tested| | TypeScript|❌ Not fully tested|

Functions

calculateCodeMetrics(filePath)

Calculates the code metrics of a code file at the specified filePath.

filePath (string): The path to the code file.

Returns an object with the following properties:

linesOfCode (number): The total number of lines of code in the file.

functions (number): The total number of functions/methods defined in the file.

complexity (number): The complexity score of the code file.

language (string): The programming language of the code file.

errors (array): An array of error objects, if any parsing errors or

unsupported language errors occur. Each error object has the following properties:

type (string): The type of the error (e.g., "Parsing Error", "Language Error").

message (string): The error message.

line (number): The line number where the error occurred.

column (number): The column number where the error occurred.

Examples

Example 1: Calculating Code Metrics

const calculateCodeMetrics = require('code-metrics');

const filePath = 'path/to/your/code/file';
const metrics = calculateCodeMetrics(filePath);

console.log(metrics);

Output;

{
  linesOfCode: 123,
  functions: 5,
  complexity: 10,
  language: 'JavaScript',
  errors: []
}

Example 2: Handling Parsing Errors

const calculateCodeMetrics = require('code-metrics');

const filePath = 'path/to/your/code/file';
const metrics = calculateCodeMetrics(filePath);

if (metrics.errors.length > 0) {
  console.log('Parsing errors occurred:');
  metrics.errors.forEach((error, index) => {
    console.log(`Error ${index + 1}:`);
    console.log('Type:', error.type);
    console.log('Message:', error.message);
    console.log('Line:', error.line);
    console.log('Column:', error.column);
  });
}

Output (if parsing errors occur):

Parsing errors occurred:
Error 1:
Type: Parsing Error
Message: Unexpected token '<'
Line: 1
Column: 1