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

jscrs

v0.2.6

Published

comment-rate-statistics

Downloads

32

Readme

Code comment rate statistics

中文版请移步README.zh-cn.md

Mainly used for front-end code comment rate statistics, and also supports other development languages

Installation

$ npm install jscrs -g

Usage

$ npx jscrs

or

$ jscrs

options

Custom configuration is not recommended

config

Configuration file, the file must be in json format. The configuration file supports the same options as cli options

  • Cli options: --config, -c
  • Type: path
  • Default: null

For example, custom configuration file

$ jscrs -c /config/jscrs/config.json

Ignore case

Whether to enable the ability of ignoring related files and directories in the .gitignore file

  • Cli options: --gitignore, --g,
  • Type: boolean
  • Default false

Output

Output path for generating html and json reports

  • Cli options: --output, -o
  • Type: path
  • Default: ./report/

config file

strongly recommended

Please create a new .cr.config.json file in the root directory of the project and write custom configuration

{
  "ext": [
    "ts",
    "tsx",
    "js",
    "jsx",
    "vue",
    "html",
    "md" // bingo, md file is recognized as comment
  ],
  "path": [
    "/src"
  ],
  "ignore":[
    "/dist/**",
    "dest/**",
    "./node_modules/**",
    "test/**",
    "data/**",
    "src/doc/**",
    "doc",
    "entries/",
  ]
}

If the file is not added, and the custom configuration file location is not specified in the bash command, the default configuration items are used, and the default items are mainly the following

{
    ext: [
      'ts',
      'tsx',
      'js',
      'jsx',
      'vue',
      'html',
      'css',
      'less',
      'scss'
    ],
    path: [process.cwd()],
    ignore: [
      '/dist/**',
      'dest/**',
      './node_modules/**',
      'test/**',
      'data/**',
      'src/doc/**',
      'doc',
      'entries/'
    ],
    reports: ['console', 'html', 'json'],
    gitignore: false,  // 默认不启用该功能
    output: './report' // 默认输出目录
  }

JSCRS Reporters

support console, html, json

API

Provide API for easy integration

import {
  IOptions,
  IAnalysis,
  IReport,
  analysis
} from 'jscrs';

const options: IOptions = {};

const ana: IAnalysis = new analysis(options);

/**@return IReport*/
const report: IReport = ana.statisticCommentRate();

/**IReport to log*/
ana.generateReports();