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

quicken

v1.1.1

Published

Speed up slow-to-start CLI commands

Downloads

2

Readme

quicken

npm CI Status dependencies Status devDependencies Status

Speed up slow-to-start CLI commands

CLI tools like ESLint, and its many wrappers, are slow mainly due to how long it takes to load all of the configured plugins. This loading cost is incurred every time the command is run.

quicken caches the loaded code in a long-running process so that the loading cost is incurred exactly once.

Usage

Install quicken by running:

yarn add quicken

quicken assumes that the command is a bin provided by a package installed in the current project, e.g., ./node_modules/.bin/xo provided the by xo package. It also assumes that the bin is a JavaScript file.

Node.js caches all imported files; so, after running a command once, running it again requires first clearing from cache the files that need to be re-evaluated. quicken will clear the executable file but will not know about other files that need to be cleared. Let quicken know about these files, by module path, by adding to package.json:

{
  "quicken": {
    "xo": [
      "xo/cli-main.js"
    ]
  }
}

If no additional files need to be cleared, leave the array empty.

Then, create wrappers for the configured commands by running:

quicken

The wrapped commands should behave exactly like the original commands.

The wrapped commands spawn a background process. To stop that process, run:

quicken stop