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

inject-code

v1.0.0

Published

inject content into file

Readme

Injector

This package aims at injecting content (mostly code) into files at specific locations.

Usage

const inject = require('inject-code');

inject(
  // your content as a string
  'your_content',

  // opts
  {
    
    // path to file where to inject content
    into: '/path/to/dest/file',
    // OR content string containing tags
    intoStr: '...',

    // tags
    // insert between these two tags (this will remove anything that is written between them)
    between: {
      starttag: '// injectcode:start',
      endtag: '// endinjectcode'
    },
    // OR insert before this tag
    before: '// injectcode',
    // OR insert after this tag
    after: '// injectcode',

    // use synchronous api (default is false)
    sync: true,

    // content must be treated as code
    // using this option will preserve indentation for multilined content
    // (based on the indentation of the given tag, or starttag).
    // this is the default
    contentType: 'code',

    // detect new line parameter (crlf or lf) and automatically converts into result string.
    // if no new lines are found, 'lf' is the default.
    // this option is ignored if the contentType option is not 'code'.
    // values:
    // - 'auto' (auto detect)
    // - 'lf' or '\n' (unix style)
    // - 'crlf' or '\r\n' (windows style)
    newLine: 'auto'
  }
)

The between option takes precedence over the before option, which take precedence over the after option.

The into option takes precedence over the intoStr option.

Return value

By default, the inject function is asynchronous and returns an ES6 Promise.

If you set the sync option to true, the function will use the node synchronous API and return undefined (or the final string if the intoStr option is specified instead).

Using the asynchronous API, the resolve function will be called with no argument if into is a valid file, or the result string ìf the intoStr option is specified instead.

Errors

Using the synchronous API, errors will be thrown using throw new Error(). Using the asynchronous API, errors will be sent to the reject method and you can catch them like you would with a simple Promise.