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

@samuraijane/pluralit

v0.0.4

Published

Convert singular English nouns to plural ones.

Downloads

6

Readme

@samuraijane/pluralit

To test locally

Create two directories that are siblings to each other and link them together. Linking mimics npm i to create a node_modules directory. pluralit can be consumed with either import or require syntax; however, when testing locally in Node, the file extension for each must be .mjs or .ts, respectively.

  1. Sibling #1 – pluralit/
git clone https://github.com/samuraijane/pluralit.git
cd pluralit
npm link
  1. Sibling #2 – consuming/
mkdir consuming
cd !$

# for `import` syntax
touch index.mjs

# for `require` syntax
touch index.ts

npm link @samuraijane/pluralit
  1. Populate the index file and save
// index.mjs
import { pluralit } from "@samuraijane/pluralit";
// or if using index.ts
const { pluralit } = requre("@samuraijane/pluralit");

console.log(pluralit("book"));
  1. Run the code
node index.ts

# or

node index.mjs
  1. To unlink, follow the steps below
cd pluralit
npm unlink
cd ../consuming
npm unlink --no-save @samuraijane/pluralit

Built with the help of Matt Pocock

pluralit is not intended to be used in production. It was built while following an excellent tutorial pulished by Matt Pocock. You can also see the notes I made while following his video.