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

sj

v0.0.7

Published

Declarative require for your DOM

Downloads

17

Readme

sj

This module provides declarative require in your DOM markup.

Example

This markup will install google analytics script on your page.

<!DOCTYPE html>
<html>
  <head>
    <title>Declarative require from html</title>
  </head>
  <body xmlns:s="require:./googleAnalytics">
    <s:analytics domain='my.site.com' ua='UA-XXXXXXXX-1'/>

    <script src="bundle.js"></script>
  </body>
</html>

Notice special namespace on our body tag? When sj parses xml it finds all custom prefixes and checks if their URN starts with require:XXX. This gives it a hint where to look actual analytics export when it comes across s:analytics tag. In this case it's relative file, googleAnalytics.js:

// googleAnalytics.js:
module.exports.analytics = function (root) {
  var domain = root.attributes.getNamedItem('domain').nodeValue;
  var ua = root.attributes.getNamedItem('ua').nodeValue;

  // this is standard google analytics include script:
  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
  })(window,document,'script','//www.google-analytics.com/analytics.js','ga');

  ga('create', ua, domain); // except that we pass our own arguments here
  ga('send', 'pageview');
}

To make this all work we browserify our input files into a bundle:

sj index.html > bundle.js

Under the hood sj binary finds all xmlns requires, and uses browserify to create a bundle.

Note: sj runtime is super tiny. As of this writing it's less than 100 lines of unminified code. This entire google analytics example is only 121 lines long, unminified. That maps to 2KB of gzipped, unminified code. Check network requests on this demo page: google analytics tag.

With this tiny size it gives you incredible power: Anyone can use custom dom elements via simple npm install ... command.

install

With npm do:

npm install sj

license

MIT