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

rig-html

v1.2.0

Published

A simple command-line tool to build the all the JS files referenced in a JSP through closure-compiler (it that's your thing)

Downloads

3

Readme

rig-html

This is a simple tool that can read HTML (or JSP) input from stdin and find all the <script></script> tags coming in. It will then identify any files that are referenced in the script tag and attempt to reconcile that against the local filesystem (using --path options).

NPM

Example Usage

The following example contatenates a.html and b.html through to rig-html and resolve files referenced against a couple of paths.

cat a.html b.html | rig-html --path scripts/ --path vendor/lib/

This would then generate a list of scripts (with absolute path) that have been found as existing in the two HTML docs, e.g:

/full/path/to/project/vendor/lib/jquery.js
/full/path/to/project/scripts/app.js

This may not seems terribly useful on it's own, but when you combine it with xargs it becomes quite magical:

cat a.html b.html | rig-html --path scripts/ --path vendor/lib/ | xargs cat

Which would then generate the entire output of the contatenated files :)

Why?

It should be noted that this tool only exists to make it easier to work with "old school" HTML page development flow. It's probably not recommended for a new project, as you should definitely consider something like browserify or webpack.

License(s)

MIT

Copyright (c) 2015 Damon Oehlman [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.