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

eslint-plugin-old-c-programmer

v1.0.1

Published

An opinionated eslint plugin for grumpy old men that grew up on the C programming language

Downloads

12

Readme

Hrmph. Kids these days with their loud music and weird coding styles.

This is my eslint style, based on how things were in the good ole days when people still used K&R:

  • Strings use double quotes. Single quotes are for characters.
  • Semicolons aren't optional. You skip a semicolon and yer code won't compile.
  • Indent is 4 spaces. Don't make me squint to see yer code blocks. Don't like it? Get a bigger monitor. Back in my day, monitors were 80 characters wide and we still used 4 spaces.
  • Include documentation in yer code. I can't remember what I had fer breakfast, don't make me try to remember what my code does.
  • Eat your veggies and write tests.

Don't like it? I don't wanna hear yer jibberjabber. Shaddup and move along before I put some rocksalt in my shotgun.

And just be happy that I didn't limit the line lengths to 80 characters...