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

@ezetech/eslint-config

v4.8.0

Published

Sharable eslint config

Downloads

108

Readme

eslint-config

Sharable eslint config

development

  npm install

Install the correct versions of each package, which are listed by the command:

npm info "@ezetech/eslint-config@latest" peerDependencies

More info: ESLint sharable configuration

To publish NPM package:

  • Make sure you have empty working status and the working directory is clean
git status --porcelain
  • Pull the latest changes
git checkout main
git pull origin main
  • Update the version in package.json and package-lock.json files with next commands. For major version (^.0.0) use next command
npm version ---no-commit-hooks major

For minor version (0.^.0) use next command

npm version --no-commit-hooks minor

For patch version (0.0.^) use next command

npm version --no-commit-hooks patch

Commit and push changes.

  • Push new tag version.
git push origin <new_version>
  • Publish a public package
npm publish --access public

Note: npm publish require authorization. For NPM access ask PM.

  • Publish a private package
npm publish --access restricted --@ezetech:registry=https://npm.pkg.github.com

Note: npm publish require Github token.

NOTICE: you NEED to publish both versions: public and private