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

unibundle

v0.2.1

Published

simple universal application bundler

Readme

unibundle

simple universal application bundler

features

  1. hmr server & client bundles
  2. live-reload browser
  3. minimal config
  4. byo directory structure
  5. stardard js linting
  6. postcss

install

npm i unibundle --save-dev

usage

unibundle consists of two commands, a config file, and a tiny snippet of server code

dev

unibundle
  • watch + compile + HMR server & client bundles
  • watch + compile + HMR css, if provided

production

unibundle build
  • compile + minify server & client bundles
  • compile + minify css, if provided

config

module.exports = production => ({
  lint: true, // default
  buildDir: 'build',
  publicDir: 'public',
  css: {
    output: {
      filename: 'style.css'
    }
  },
  client: {
    entry: 'app/index.js',
    output: {
      filename: 'index.js'
    },
    rules: [],
    alias: {},
    plugins: []
  },
  server: {
    entry: 'server/index.js',
    output: {
      filename: 'server.js'
    },
    rules: [],
    alias: {},
    plugins: []
  }
})

server set-up

your server should use the following as an entry point, just copy and paste:

const http = require('http')
let app = require('./server.js').default // YOUR APP
const server = http.createServer((req, res) => app(req, res))
const PORT = process.env.PORT || 3000

server.listen(PORT, e => {
  if (e) console.error(e)
  console.log(`node server listening at port ${PORT}`)
})

if (module.hot) {
  module.hot.accept('./server.js', () => {
    app = require('./server.js').default
  })
}

the server.js file in this example should export a function with the signature (request, response) => {} a la connect-based libraries

// server.js
import connect from 'connect'
import router from 'router'

const app = connect()
const routes = router()

routes.get('*', (request, response) => {
  response.writeHead(200, {
    'Content-Type': 'text/plain'
  })
  response.write('tacos')
  response.end()
})

app.use(routes)

export default app

client set-up

in your client be sure to add the usual, or similar:

if (module.hot) module.hot.accept()

client bundle

unibundle serves the client bundle at http://localhost:8080/index.js, so be sure to link to that during dev. For production, point it to your configured public path.

babel

include a .babelrc in your root and install presets/plugins to your project

css

if you opt to use the built in postcss compilation, you'll need to add a postcss.config.js to the root of your project, and import your stylesheet into your client bundle, as per usual

run your dev server

you still need to run your server during dev:

node dist/server.js # or wherever

prior work

License

MIT License © Eric Bailey