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

freelint

v4.0.0

Published

a lint tool based on standard-engine, and configuration is based on Airbnb

Downloads

180

Readme

freelint

Build Status

a lint tool based on standard-engine and rules follow the Airbnb javascript standard.

We are followed SamVer 2.0, this started from version 2.0.0, then we will try our best to avoide the dependency hell.

Install (Global)

npm install -g freelint

or use yarn

yarn global add freelint

Install (Local)

npm install freelint --save-dev

or use yarn

yarn add freelint --dev
# ...
# Add npm task in package.json.
"script": {
  "freelint": "freelint",
  ...
}

Usage (Global)

In your project's directiry.

freelint

Usage (Local)

npm run freelint

or use yarn

yarn run freelint

That's all.

Know Issues

  1. If you are using ES6 import/export feature, and webpack like build tool with a resolve setting, you should extract the resolve settings to a new file named webpack.resolve.js, and place it to config dir in root dir, we know it's a dirty code, if you have any good solution, don't hesitated to create a pull request.(e.g.Demo)

How do I make the output all colorful and pretty?

snazzy is the default output format for cmd freelint now, you can also use any other format library, just need to use the base cmd freelint-base, like:

$ freelint-base | customFormat

How do I ignore files?

The paths node_modules/**, *.min.js, bundle.js, coverage/**, hidden files/folders (beginning with .), and all patterns in a project's root .gitignore file are automatically ignored.

Sometimes you need to ignore additional folders or specific minified files. To do that, add a freelint.ignore property to package.json:

"freelint-base": {
  "ignore": [
    "**/out/",
    "/lib/select2/",
    "/lib/ckeditor/",
    "tmp.js"
  ]
}

TODO

  • [ ] Add reporter function by setting from cli