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

browsermodules

v0.0.1

Published

package node module style files for the browser

Downloads

3

Readme

browsermodules

a very slim wrapper which allows you to structure your code like node.js modules. they will be combined to a single file which can be consumed by browsers.

build status

Build Status

usage

cli

browserModules --in index.js --out combined.js

Options:
  -i, --in    input file             [required]
  -o, --out   output file            [required]
  -e, --eval  use sourceURL feature

module

var browsermodules = require('browsermodules')
browsermodules({
  // required
  in: path.resolve(__dirname, './index.js'),
  out: path.resolve(__dirname, './out.js'),
  // optional
  eval: true,
  close: function() { console.log('output complete'); }
});

tradeoffs

you can use

  • module
  • exports

but there is no support for:

  • __filename
  • __dirname
  • node internals like process and Buffer