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

plog

v0.3.0

Published

p - A small global logging utility for faster debugging

Downloads

100

Readme

Your new best friend when developing, and probably ONLY for development

version license

🐞 p()

p('Awesome!!')          // Logs awesome

fetch('https://cats')
.then(x => x.json())
.then(p)                // Logs the json result
.then(store)

a.neat().p.chain.p.here // Logs result of `neat` and `chain`

const wat = p`wat`

wat('is going on')      // Logs `wat is going on`

This module adds a global p and global plog* variable which is a convenience method for logging.

It simply defers to console.log, but returns the first argument instead of undefined.

If it is called as a tagged template literal it will return a new p function that always prefixes logs with the value in the template literal.

It also adds p and plog to Object.prototype to enable even quicker logging. This way you can jump into a chain at any place to log the value and continue with your program as if nothing happened.

* (for times when p is shadowed)

Example require

Node at launch
node -r plog index.js   # -r option is short for --require
Browser
<script src="https//unpkg.com/plog">
Node in file
require('plog')         // Adds the global p
Node global

You can use plog in place of node which is just a shortcut for node -r plog ...

plog index.js