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 🙏

© 2025 – Pkg Stats / Ryan Hefner

merco

v0.1.10

Published

Merging, compressing and cache busting for js

Readme

Build Status

Merco is Express middleware for merging and minifying JS files in run time. It also support cache busting.

How to use it ?

install merco module:

  • npm install merco

use merco as middleware:

  • app.use(merco.init(params));

set route from which you want to serve files:

  • app.get('/build/*', merco.route);

use it in template (.ejs):

<% getJS('PATH/TO/FILE1') %>
<% getJS('PATH/TO/FILE2') %>

<%- printJS() %>

Params

route - route from which you want to serve files

version - cache buster, good practice is to use package.version

filePath - location of raw js files

buildPath - location where processed files should be stored (need write permissions on that folder)

sKey - secret key that will be used for encryption

cache - default true, in dev environment set cache to false

ignoreSameFile - default true, ignores same file while registering with getJS()

async - default false, includes async attribute to script tag. More about it here

Testing

npm run test

Why run time ?

  • in case of large application and big number of files doing this in run time is much more convinient
  • this is also useful in case of multivariant tests when we want to have different js for different variants
  • it's easier to use in some case

Notes

For better performance use caching on nginx or akamai.