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

hexty

v1.0.2

Published

A minimalistic tool for text replacement in HTML

Readme

Hexty

A minimalistic tool for text replacement in HTML.

Install

npm i hexty -D

Example

There is a working example in the example folder.

Let's create the config file. It will contains the config object and the files list, both constants must be exported, like in the example.

For example in this case the index.html page will use the index.texts.js file.

textly.config.js

const path = require('path');

const files = [
    {
        path: path.resolve(__dirname, "./index.html"),
        text_path: path.resolve(__dirname, "./index.texts.js")
    }
];

const config = {
    attr_start: "data-texty"
}

module.exports = {
    files: files,
    config: config
};

let's create the index.texts.js file, which is a map of placeholder and text files

index.texts.js

const texts = {
    "hello-message": "Hello World"
}

module.exports = texts;

the html contains a p tag with attribute data-textly with value hello-message matching the key in index.texts.js.

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="UTF-8">
        <meta name="viewport" content="width=device-width, initial-scale=1.0">
        <meta http-equiv="X-UA-Compatible" content="ie=edge">
        <title>Document</title>
    </head>
    <body>
        <h1>Texty example</h1>

        <p data-texty="hello-message">Hello World</p>

    </body>
</html>

At last, let's create the index.js file that glues everything together

index.js

const config = require('./textly.config');
const textly = require('hexty')(config);