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

@poap/skunk-linter

v0.0.3

Published

Linting and styleguide for team skunk

Downloads

21

Readme

ESLint declarations for team skunk

A shared set of standards and preferences, enforced through eslint and vscode.

Quickstart

To use:

  1. npm install -D @poap/skunk-linter @babel/eslint-parser eslint eslint-plugin-react husky
  2. Copy .eslintrc.js to your project's .eslintrc.js
  3. Copy .babelrc to your project's .babelrc
  4. Copy .vscode/settings.json to your project's .vscode/settings.json
  5. Copy .husky/pre-commit to your project's .husky/pre-commit
  6. Run husky initial setup

Lazy shell

npm install -D @poap/skunk-linter @babel/eslint-parser eslint eslint-plugin-react husky
mkdir .vscode .husky

# Download files
curl https://raw.githubusercontent.com/poap-xyz/skunk-linter/main/.eslintrc.js --output .eslintrc.js
curl https://raw.githubusercontent.com/poap-xyz/skunk-linter/main/.vscode/settings.json --output .vscode/settings.json
curl https://raw.githubusercontent.com/poap-xyz/skunk-linter/main/.husky/pre-commit --output .husky/pre-commit
curl https://raw.githubusercontent.com/poap-xyz/skunk-linter/main/.babelrc --output .babelrc
git add -f .eslintrc.js .babelrc .vscode/* .husky/*
chmod ug+x .husky/*
npm pkg set scripts.prepare="husky install"
npm pkg set scripts.lint="eslint --fix src"
npm run prepare
npx husky add .husky/pre-commit
git add .husky/pre-commit

Making changes

The relevant source files are in modules/. If you make a change, you can update the package by:

  1. Making the changes
  2. Updating the version number in package.json
  3. Pushing to the main branch of the repo or opening a pull request