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

vernacular

v0.1.0

Published

Industry-specific vocabulary customization for JS/TS apps — i18n, but for industry verticals.

Readme

vernacular

Industry-specific vocabulary customization for JS/TS apps. Like i18n, but the dimension is industry (CRM "leads" → education "students", healthcare "patients") rather than language.

Install

npm install vernacular

If you'll use the React adapter, you also need React 18+:

npm install vernacular react

Core usage

import { createVernacular } from 'vernacular';

const packs = {
  education: {
    lead: { one: 'student', other: 'students' },
    deal: { one: 'enrollment', other: 'enrollments' },
  },
  healthcare: {
    lead: { one: 'patient', other: 'patients' },
  },
};

const { v, setIndustry } = createVernacular({ packs, industry: 'education' });

v('lead');                 // "students"
v('lead', { count: 1 });   // "student"
v('company');              // "company"  (no override; key is the default)

setIndustry('healthcare');
v('lead', { count: 1 });   // "patient"

React

import { VernacularProvider, Term, useVernacular } from 'vernacular/react';

<VernacularProvider packs={packs} industry="education">
  <App />
</VernacularProvider>

// In a component:
<h1>Your <Term name="lead" count={2} /></h1>

// Or via hook:
const v = useVernacular();
return <h1>Your {v('lead', { count: 2 })}</h1>;

Casing helpers

v() returns a plain string — use native methods (.toUpperCase(), .toLowerCase()) directly. For title/sentence case:

import { titleCase, sentenceCase } from 'vernacular';

titleCase('your ' + v('lead'));     // "Your Students"
sentenceCase('your ' + v('lead'));  // "Your students"

TypeScript

Untyped works out of the box. For typed keys, augment the module:

// vernacular.d.ts
import 'vernacular';
declare module 'vernacular' {
  interface VernacularVocab {
    vocab: 'lead' | 'deal' | 'company';
  }
}

Now v(), <Term name>, and useVernacular() all autocomplete and reject typos.

License

MIT