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

stringting

v0.0.9

Published

Tools for building internationalised templates

Readme

stringting NPM version

very alpha

String build tool for internationalisation i18n.

Quick overview

Take a template like:


html
  head
    title __(app.title)
  body
    h1 __(app.heading)
    p __(app.intro)

run stringting

And generate a translations file like:


{
  app: {
    title: {
      locations: ['app.jade:3'],
      msgid: "__(app.title)",
      msgstr: "",
      comments: ""
    },
    heading: {
      locations: ['app.jade:5'],
      msgid: "__(app.heading)",
      msgstr: "",
      comments: ""
    },
    intro: {
      locations: ['app.jade:6'],
      msgid: "__(app.intro)",
      msgstr: "",
      comments: ""
    }
  }
}

Then add some text for your keys like:


{
  app: {
    title: {
      locations: ['app.jade:3'],
      msgid: "__(app.title)",
      msgstr: "Demo site",
      comments: ""
    },
    heading: {
      locations: ['app.jade:5'],
      msgid: "__(app.heading)",
      msgstr: "Demonstrating Stringting",
      comments: ""
    },
    intro: {
      locations: ['app.jade:6'],
      msgid: "__(app.intro)",
      msgstr: "Just a quick little demo.",
      comments: ""
    }
  }
}

Run stringting again and get a template like:


html
  head
    title Demo site
  body
    h1 Demonstrating Stringting
    p Just a quick little demo.

Set up

To run stringting you will need a .stringtingrc file at your project root.

The minimum settings you will need to run a build are:

src

Path to your master templates. e.g.


"src": "src/templates"

translations

Path to your json translation files. e.g.


"translations": "src/translations"

locales

The locales to map translations and production templates to. e.g.


"locales": ["dev", "en", "fr"]

templates

Destination folder for your final compiled templates.


"templates": "views"

All together

So your finished .strintingrc file would look something like:


{
  "src": "src/templates",
  "translations": "src/translations",
  "locales": ["dev", "en"],
  "templates": "views"
}

Running it

If you have Stringting installed as a project dependency you will most likely want an npm or gulp task that runs the command:


node node_modules/stringting/bin/stringting

Or you might have it installed globally then you can just run:


stringting