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

postbuild

v2.1.0

Published

A command line utility to inject css and js files into an html file or to remove code based on conditions.

Downloads

498

Readme

A command line utility to inject css and js files into an html file or to remove code based on conditions.

Inspired by gulp-inject and gulp-remove-code and written because I could not find a command-line equivalent that could work with npm scripts instead of gulp.

This module injects css and javascript files between markers placed in an html file or removes code between markers. It can take a single file or a directory of files which will be transformed to strings and injected. It removes code between markers so you can for example remove livereload code which is not needed in a production environment. It can also inject the current git commit hash into the HTML as a comment so it is easily visible which commit is currently deployed.

This module was written in ES6 and requires node >= 4.0.0.

Usage

Place the markers in your html file to inject or remove code:

   <!DOCTYPE html>
   <html>
   <head>
     <title>Home</title>

     <!-- inject:css -->
     <link rel="stylesheet" href="/path/to/styles.css">
     <!-- endinject -->

   </head>
   <body>

     <!-- inject:js -->
     <script src="/path/to/build.js"></script>
     <!-- endinject -->

     <!-- remove:production -->
     <script src="http://localhost:35729/livereload.js?snipver=1"></script>
     <!-- endremove -->

   </body>
   </html>
   <!-- inject:git-hash -->

The css and javascript files will be injected between the markers and the scripts and stylesheets that are already there will be removed. This way you can replace the regular files used in a development environment with the built files (bundled, minified, versioned) in a production environment.

Options:

-h, --help             output usage information
-V, --version          output the version number
-i, --input <input>    Input file
-o, --output <output>  Output file (defaults to input when omitted)
-c, --css <css>        css file(s) to inject (file or directory). Wildcards can be used with quotation: '**/*.css'
-j, --js <js>          js file(s) to inject (file or directory). Wildcards can be used with quotation: '**/*.js'
-r, --remove <remove>  Remove condition
-g, --ignore <path>    Prefix to remove from the injected filenames
-H, --hash             Inject git hash of current commit
-e, --etag             Appends "?etag=fileHash" to every import (link, script) to avoid undesired caching in new deployments

Examples

Given a directory:

-- dist
   -- css
      styles.1234abc.css
   -- js
      vendor.js
      build.4567def.js

postbuild -i index.html -o dist/index.html -c dist/css -j dist/js -r production -H

will result in the file dist/index.html:

   <!DOCTYPE html>
   <html>
   <head>
     <title>Home</title>

     <!-- inject:css -->
     <link rel="stylesheet" href="dist/css/styles.1234abc.css">
     <!-- endinject -->

   </head>
   <body>

     <!-- inject:js -->
     <script src="dist/js/vendor.js"></script>
     <script src="dist/js/build.4567def.js"></script>
     <!-- endinject -->

   </body>
   </html>
   <!-- b64f022ae51d87a411c4608f403f3216ee028d03 -->

Notice that the code

     <!-- remove:production -->
     <script src="http://localhost:35729/livereload.js?snipver=1"></script>
     <!-- endremove -->

has been removed.

The comment

    <!-- inject:git-hash -->

has been replaced by the git hash of the current commit.

Specifying a single file instead of a directory will only inject that single file:

postbuild -i index.html -o dist/index.html -c dist/css -j dist/js/build.4567def.js -r production

results in:

   <!DOCTYPE html>
   <html>
   <head>
     <title>Home</title>

     <!-- inject:css -->
     <link rel="stylesheet" href="dist/css/styles.1234abc.css">
     <!-- endinject -->

   </head>
   <body>

     <!-- inject:js -->
     <script src="dist/js/build.4567def.js"></script>
     <!-- endinject -->

   </body>
   </html>

Notice that vendor.js is not injected.

If the -e, --etag is specified the output will be

   <!DOCTYPE html>
   <html>
   <head>
     <title>Home</title>

     <!-- inject:css -->
     <link rel="stylesheet" href="dist/css/styles.1234abc.css?etag=e997365235369248a234b1c343ac41">
     <!-- endinject -->

   </head>
   <body>

     <!-- inject:js -->
     <script src="dist/js/build.4567def.js?etag=9fffaf9de332d9848ab34bbc3434d34341"></script>
     <!-- endinject -->

   </body>
   </html>

Tests

Run npm test to run the tests.