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

@sidekick/analyser-common

v1.0.2

Published

Handles input for analysers. Also defines the protocol which other programs can follow - no dependencies on JS

Downloads

9

Readme

analyser-common

Build Status

Module that provides stdin input in a pre-defined way to a Sidekick analyser.

Provides analysers with a setup object that contains:

  • config (any configuration file contents for the analyser, e.g. .eslintrc file contents)
  • contents (the contents of the file to be analysed)
  • filePath (the file path of the file to be analysed)

You can easily write your own analysers for use with Sidekick. Sidekick analysers can be written in any language; all you need to do is accept input via stdin and provide output via stdout.

Installation

npm install --save @sidekick/analyser-common

Usage

var sidekickAnalyser = require("@sidekick/analyser-common");
sidekickAnalyser(function(setup){
  //run the analyser
});