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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@rooknj/eslint-config

v1.1.1

Published

eslint base config for my typescript projects

Downloads

3

Readme

Eslint Config Rooknj

Build Status npm version code style: prettier semantic-release

My Personal Eslint Config for Typescript-React applications

Installing

Prerequisites

  • NodeJS LTS installed on your system (Check by running node -v)

Install with Yarn or NPM

yarn:

yarn add -D @rooknj/eslint-config \
        eslint-plugin-jest@^24.0.2 \
        [email protected] \
        eslint-plugin-import@^2.22.0 \
        eslint-plugin-jsx-a11y@^6.3.1 \
        eslint-plugin-react@^7.20.3 \
        eslint-plugin-react-hooks@^4.0.8 \
        @typescript-eslint/eslint-plugin@^4.0.1 \
        @typescript-eslint/parser@^4.2.0

npm:

npm install --save-dev @rooknj/eslint-config \
            eslint-plugin-jest@^24.0.2 \
            [email protected] \
            eslint-plugin-import@^2.22.0 \
            eslint-plugin-jsx-a11y@^6.3.1 \
            eslint-plugin-react@^7.20.3 \
            eslint-plugin-react-hooks@^4.0.8 \
            @typescript-eslint/eslint-plugin@^4.0.1 \
            @typescript-eslint/parser@^4.2.0

Developing

Prerequisites

  • NodeJS LTS installed on your system (Check by running node -v)
  • Yarn (Check by running yarn -v)

Deploying

Deployments happen automatically using Semantic-Release based off of conventional commit messages

Commit Messages

Commit messages must follow Conventional Commits

Example Messages

  • chore(docs): updated Readme
  • refactor: renamed index.js
  • fix(scope): fixed bug
  • feat: Added new ability in code
  • BREAKING CHANGE: Removed deprecated functions

CI will fail if you do not use the correct commit format. Local messages are linted using Commitlint

Commitizen support coming soon

Versioning

We use SemVer 2.0.0 for versioning. To see available versions, check out the releases page

Code Style

Code style is managed by Prettier code style: prettier

All default prettier styles are enabled except for the overrides located in .prettierrc.js

Prettier is automatically ran on staged files every commit using Husky and Lint-Staged

You can run prettier manually on every file through the command yarn reformat or you can set up prettier to run inside your IDE/Editor

License

This project is licensed under the terms of the MIT license.