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

injectml

v1.2.3

Published

A simple package that injects html to other html files

Readme

Injectml

WARNING: This package was built for learning purposes only.

A simple package that injects html to other html files using a special <inject> tag.

Quick Start

To start using Injectml, specify an input and an output on your command like so:

  npm i -D injectml
  injectml input="src" output="dist"

Note that both the input and output argument will be relative to the root of the project. Injectml will also keep the output's file structure the same as it was in the input folder.

To inject an html file, we use the <inject> tag. Let's say we had a file structure like so:

src
  - index.html
  - components
    - navbar.html

To inject navbar into index, we need to specify inside our index.html where to place the navbar and point towards it:

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Injectml</title>
  </head>
  <body>
    <inject src="components/navbar.html">
  </body>
</html>

This would then inject navbar's contents into our index html file.

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Injectml</title>
  </head>
  <body>
    <nav>
      You've injected me inside!
    </nav>
  </body>
</html>

Note that an html file that has been used as an injection will not be placed into the output path, so our output folder structure will look like this:

dist
  - index.html

Notice how the components folder and the navbar html file is not present.

Process

There are three main parts when running injectml, we first have reading, then injecting, then writing

  • reading is where we will map every file inside the input path specified and get them ready for the injecting and writing process.

  • injecting is where we will run through all the contents grabbed from reading, recursively check if it is injecting other html files, until we finish injecting all of them.

  • writing after we have the content of our files ready, we then write them to the output path specified. keeping the same structure as it was in the input folder.

Additional Notes

Injectml uses pretty inside the hood.

You can also use injectml in your modules.

const injectHTML = require('injectml');

const modifiedHTML = injectHTML({ input: "./src", output: "./dist" });