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 🙏

© 2026 – Pkg Stats / Ryan Hefner

mohammedkhan

v4.4.0

Published

> Get to know Mohammed via npm. Just run npx mohammedkhan

Downloads

7

Readme

npx mohammedkhan

Get to know Mohammed via npm. Just run npx mohammedkhan

Usage

To use this CLI run the following command


npx mohammedkhan 

Steps for ESlint Integration process:

Verify Your Project Setup

Open your project in Visual Studio Code. Ensure that your project directory contains a valid package.json file. Ensure you can open an integrated terminal running a bash/zsh shell in the root folder.

Install ESLint

Install ESLint as a development dependency using npm.


npm install eslint --save-dev

After running this command, ESLint will be listed under devDependencies in your package.json file, and you can configure it according to your project’s requirements.

Run ESLint Initialization

In the integrated terminal, run the ESLint initialization command.


npm init @eslint/config

Follow the interactive prompts to answer configuration questions tailored to your project.

ESLint finishes resulting in an eslint.config.mjs file.

If needed, you can run this init script again if you need to change any answer.

Configure the Generated File

Open the generated eslint.config.mjs file in Visual Studio Code.

Review the default settings and adjust them as necessary to match your project’s coding style and requirements.

Ensure that the configuration includes all desired rules and plugins relevant to your project.

Add a Lint Script to package.json

Open your package.json file in Visual Studio Code.

Add a script entry that allows you to run ESLint on your code.

Ensure the commas is configured correctly to target the files you wish to lint.


"scripts": {
    "test": "echo \"error: no test specified\" && exit 1",
    "lint": "eslint index.js"

},

Run the Linting Process

Use the integrated terminal to execute the lint script you added.


npm run lint

or use npx


npx eslint index.js

Review the output carefully, noting any issues that ESLint reports.

Fix Reported Issues

Address each linting error or warning by updating your code accordingly.

Continue running the lint command until your code passes all linting checks.

Repeat this as needed when you add more code to this project.