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

sc-eslint

v1.3.7

Published

A small wrapper of eslint, pre-configured to StoneCypher's preferences. MIT licensed.

Downloads

102

Readme

sc-eslint

A small wrapper of eslint, pre-configured to StoneCypher's preferences

Language   Platform   License   Status

NPM Downloads

What?

This is two things:

  1. drop and run eslint -c node_modules/sc-eslint/sc-eslint-config.json *.js
  2. Trivially simple gulp task

Gulp task, you say?

Trivially simple.

var lint = require("sc-eslint");
var tgts = "gulpfile.js estask.js";

lint.gulpreg(gulp, { "targets" : tgts });

And now you have a gulp task named lint, which you may use like so:

gulp.task('default', ['lint']);

Why?

Because this way, as eslint gets stronger, as my preferences evolve, etc, all I need to do is to keep one module up to date, then all dependents will be brought into line.

Which is pretty sweet, if you think about it.

But I have different preferences

Great! Don't we all? :) Make one for yourself! Here's how:

  1. Fork this repo
  2. Copy sc-eslint-config.json to your own config file
  3. Change the contents - every rule is spelled out in that file
  4. Change what lrules points to, if using the gulp task
  5. Push your own repo and your own NPM module
  6. Point back to these instructions, for others' sake

Polemic

sc-eslint is MIT licensed, because viral licenses and newspeak language modification are evil. Free is only free when it's free for everyone.