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

@yernak/global-options

v0.0.3

Published

Global options applicable to _every_ yernak sub-command

Downloads

5

Readme

@yernak/global-options

Global options applicable to every yernak sub-command

Options

--concurrency

How many threads to use when yernak parallelizes the tasks (defaults to count of logical CPU cores)

$ yernak publish --concurrency 1

--loglevel <silent|error|warn|success|info|verbose|silly>

What level of logs to report. On failure, all logs are written to yernak-debug.log in the current working directory.

Any logs of a higher level than the setting are shown. The default is "info".

--max-buffer <bytes>

Set a max buffer length for each underlying process call. Useful for example when someone wants to import a repo with a larger amount of commits while running yernak import. In that case the built-in buffer length might not be sufficient.

--no-progress

Disable progress bars. This is always the case in a CI environment.