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-config-breki

v1.0.38

Published

A handful of rules used by Breki Tomasson for formatting, error-checking and practicing Safe Hex.

Downloads

4

Readme

eslint-config-breki

Build
Status semantic-release

We spend more time reading our code than we do writing it - so it only makes sense to make it look as good as possible, right? Instead of putting all your effort into making sure that your code just works, why not add that little extra bit of effort in making sure that it also looks good? It makes it so much easier to understand when you're going back to fix whatever problems you inevitably created when you were working on that great idea you had.

My goal with this repo was originally just a place to store my various rulesets for various linters and formatters. Over time, it grew into something more, and also something less, than that. This is now a full eslint configuration that I can import into other projects to help me out.

Obligatory @todo section

  • [x] Still getting an error message thrown by eslint when extending this...
  • [x] Get rid of validate-commit-msg.
  • [ ] Add more tests - ideally two or three for each defined rule.
    • Mental note: Remember to test both the positive and negative for each rule
  • [ ] See if there is any way for the same package to export both Eslint and, for example, Tslint or Stylelint rules.

License

Free for the world to use. My code is mainly just a wrapper for other people's hard work.

(That means MIT Licence, if you really want it spelled out.)