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

paq

v0.7.0

Published

Multithreaded tool for running node.js style code in the browser inspired by substack's Browserify.

Downloads

20

Readme

paq

Build Status Coverage Status

paq implements a subset of Browserify's features with full multithreading support. For impatient people who have to deal with large codebases.

Get updates by following me on Twitter: Follow @_benng

What's Working

  • require('./relative/path')
  • require('some-module')
  • require('node-core-module')
  • require(path.join(__dirname, 'some_module')) (or any other statically resolvable expression, like __dirname + '/path')
  • Exporting a standalone bundle
  • Converting transforms like hbsfy for use with paq

What's Not Working

  • paq can't actually run transforms yet. Almost there!
  • Replacement of process.env with actual environment vars.

Usage

USAGE: paq <entry files> [options]

Options:
  --parserTasks=<integer>          The maximum number of concurrent AST parsers
  --requireTasks=<integer>         The maximum number of concurrent require
                                   evaluations
  --standalone                     Returns a module that exports the entry
                                   file's export
  --convertBrowserifyTransform     Returns a module that wraps a browserify
                                   transform for use with paq
  --ignoreUnresolvableExpressions  Ignores expressions in require statements
                                   that cannot be statically evaluated

Under The Hood

Caveats

  • Mac only for now. If you get it running elsewhere, send a PR.
  • Implements only the subset of Browserify that I need at work.
  • Browserify is a production ready, well maintained, and mature project. paq is none of those things, considering I wrote it in about 24 hours.

Contributing

To work on paq, you'll need these tools:

  • Xcode 6.2
  • OS X 10.10.2
  • xctool (Get Homebrew then brew install xctool)
  • node
  • npm

To run the tests (which require the things mentioned above) you can either run npm test from the command line, or run the paq-test target in Xcode.