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

@ryancwalsh/linting

v1.1.0

Published

My TypeScript and Prettier linting rules to keep all of my projects consistent.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

ryancwalshryancwalsh

Keywords

Readme

@ryancwalsh/linting

My TypeScript and Prettier linting rules to keep all of my projects consistent.

Get started

yarn add -D @ryancwalsh/linting [email protected] [email protected] --exact

Carefully consider running:

cp node_modules/@ryancwalsh/linting/src/examples/eslint.config.js .
cp node_modules/@ryancwalsh/linting/src/examples/prettier.config.js .
cp -R node_modules/@ryancwalsh/linting/.vscode/ .

Publishing

npm publish --access=public

TODO

Include rules from 'next/core-web-vitals' and/or 'eslint-config-next'. "eslint-plugin-storybook": "0.12.0", "prettier-plugin-prisma": "5.0.0",

TODO: Solve Could not find a declaration file for module '@ryancwalsh/linting'. '/home/rcwalsh/code/partner_portal/node_modules/@ryancwalsh/linting/src/index.js' implicitly has an 'any' type. Try npm i --save-dev @types/ryancwalsh__linting if it exists or add a new declaration (.d.ts) file containing declare module '@ryancwalsh/linting';ts(7016)

Document how to use this repo directly while developing it (how to use the local package via symlink instead of the published one).

Helpful

https://github.com/gajus/eslint-config-canonical/blob/main/COMPARISON_TABLE.md https://github.com/gajus/eslint-config-canonical/tags