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

mean-duck

v1.0.4

Published

a mean duck that may or may not motivate you to become a better developer

Downloads

7

Readme

Mean Duck

HOW TO USE ( proceed with caution - the duck ain't friendly)

  1. npm i mean-duck
const duck = require("mean-duck");
console.log(duck.help());
console.log(duck.greet());
console.log(duck.ask("question here"));

Demo of how to publish your own mini library to NPM Registry

Steps:

  1. create a git repo and README.md file
  2. go to the project folder and run npm init
  3. you can enter package name, version, description, entry point, keywords, author ... when being prompted
  4. create a index.js file and write the function to be exported

Once you are happy with your code, you can test it by doing:

Testing

  1. run npm link in the terminal ( of your project directory)
  2. create another directory and run npm link package-name ( this will install the package locally)
  3. you can now test it by running node mytest.js
// mytest.js file in another directory
const myStuff = require('my-package')
console.log(myStuff.somefunction())

Publishing

  1. npm login ( you will need to create an account first)
  2. npm publish

Issue and solution

https://stackoverflow.com/questions/59280276/npm-package-readme-display-issue/61161811#61161811