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

minilint

v0.0.14

Published

A compact linter for writing compact code

Downloads

12

Readme

minilint

Build Status

minilint is a fast and small linter. It is intended to encourage modularity.

It lints JavaScript with the following rules:

  • Max 500 lines per file
  • Max 80 chars per line
  • Max 40 lines per code block (function, array, etc)
  • Use two spaces, not tabs
  • Max six spaces at the beginning of a line
  • No end-of-line operators or semicolons
  • No opening ( or [ at the start of a line
  • Strict mode

I'm experimenting with using this on my projects. Feel free to use this as well, or not.

Installation

npm install -g minilint

Usage

minilint <path1> <path2> <...>

Note

If no arguments are passed, minilint will automatically include **/*.js and exclude node_modules/**, coverage/**, and **/*.min.js.

Options

--help -h: show help
--verbose -v: enable verbose logging
--exclude -e: exclude all paths appearing after this option

Examples

minilint
minilint file.js
minilint file.js --verbose
minilint file1.js file2.js file3.js
minilint "**/*.js" --exclude "node_modules/**"
minilint "**/*.js" -v -e "node_modules/**"

License

MIT