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-walkertracker

v1.0.2

Published

eslint config shared between reseller and wtv2

Downloads

1

Readme

Walker Trackers eslint config file

This will be a shared config file that will be used in the reseller and new UI applications so take that into consideration before making changes to this file.

If the eslint rules are specific to the project then add them in the .eslintrc within that project


Updating and Publishing the npm module

  1. Create an account on npm if you don't have one
  2. Ask a lead to invite you to the walkertracker organization that is registered with npm
  3. Once you have access, login to npm locally
npm login
  1. any changes you make, make sure to commit to this repository before publishing
  2. Next you'll need to bump up the version, so first look in package.json and check the current version
"version": "1.0.1",
  1. once you've pushed and commited your changes, within this projects root run
npm version <bump up the version>

in this case the next version would be 1.0.2

npm version 1.0.2
  1. finally run npm publish and then update the packages how you would normally would in each project