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

infestor

v0.3.0

Published

infest content into requests - via connect middleware

Downloads

53

Readme

Infestor

npm tests coverage

Inject content into your server responses

Why should you care?

There are times when all you want to do is inject a JS file or custom markup into the req res cycle without forcing the content generator to include custom markup on their side.

This is where infestor comes in. Just specify the regex insertion point and content. Then you are good to go.

Installation

npm install infestor --save

Infestor Options

  • content: A string of content to be injected into the response
  • injectAt: The location where your content will be inject at.
  • append: A boolean representing if your custom content should just be appended to the response (overrides injectAt).
  • injectContent: An overrideable method to define how your content is inserted into the response. It is naive to think that infestor can cover all of the use cases for everyone. So instead of bloating the core injection method, we provide a simple to use hook into the primary buisness logic for inserting custom content.

Usage

var http = require('http');
    connect = require('connect'),
    infestor = require('infestor'),
    serveStatic  = require('serve-static');

var app = connect()
            .use(infestor({
              content: "<h2> injected content! </h2>",
              injectAt: '/<\/html>/'
            })
            .use(serveStatic(__dirname));

var server = http.createServer(app).listen(1111)

Make sure that you place the infestor middleware before you serve your content or else infestor will not work.

License & Contributing