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

names

v1.0.0

Published

Minimal API client for uinames.com

Downloads

58

Readme

names Build Status

This package acts as an API client for my favorite generator of random names: uinames. It's perfect for prototyping stuff or examples of real names in production apps.

Usage

Install the package using npm and save it to the dependency list:

npm install --save names

Now you have two choices to interact with the package. Since it's based on the concept of promises, you can either use async/await (it hasn't yet landed in node, so you'll have to transpile the code)...

import names from 'names'

try {
  const list = await names()
} catch (err) {
  console.error(err)
}

...or the old way of doing it:

const names = require('names')()

names.then(function (list) {
  console.log(list)
})

names.catch(function (err) {
  console.error(err)
})

Both examples will result in a response that looks like the following:

{
  "name": "John",
  "surname": "Doe",
  "gender": "male",
  "region": "United States"
}

Configuration

Indipendent from which of the methods mentioned above you would like to use, you can always pass a configuration object to the module's main method:

names({
  gender: 'female',
  amount: 10
  ...
})

Here's the full list of all available options:

| Name | Description | Type | | ---- | ----------- | ---- | | amount | Amount of names to return, between 1 and 500 | Integer | | gender | Limit results to the male or female gender | String | | region | Region-specific results | String | | minLength | Require a minimum number of characters in a name | Integer | | maxLength | Require a maximum number of characters in a name | Integer |

Contribute

  1. Fork this repository to your own GitHub account and then clone it to your local device
  2. Link the package to the global module directory: npm link
  3. Transpile the source code and watch for changes: npm start
  4. Within the module you want to test your local development instance of names, just link it to the dependencies: npm link names. Instead of the default one from npm, node will now use your clone of names!