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

plunk

v0.6.0

Published

Utility to submit a directory to plnkr.co

Downloads

49

Readme

A tiny utility to post current directory contents to http://plnkr.co/edit

Anonymous Usage

  1. Go the the dir you want to plunk.
  2. Run plunk

Or plunk --dir path/to/dir --desc "A string describing the plunk" --tags "comma,separated,tags".

Authorized usage

To submit plunks under your user and to update them, you need to be authorized.

For that:

  1. Sign in to http://plnkr.co with Github (button in the right-upper corner of http://plnkr.co/)
  2. In browser developer console run: document.cookie.match(/plnk_session=(\w+)/)[1] to obtain the session id.
  3. Create ~/.plunk_config.json with the content { "auth": { "id": "..." } }, where ... means the output of step 2.

This will save an authorized session which the utility will use.

An example of ~/.plunk_config.json:

{
  "auth": { "id": "56224aba860eabcdef869189" }
}

Exclusions

  • Ignores files starting with a dot '.'

Gotchas

  • Saves current plunk metadata in the file .plunk, uses it to update the plunk properly.
  • A once-created plunk is bound to its directory name. When you copy it into a new directory (or rename), plunk will create a brand-new plunk. I found this behavior helpful, because when I clone an existing directory into a new example, it makes me sure I will not overwrite an existing plunk.
  • The --tags flag only works when creating a new plunk, not updating an existing one.
  • You should create .plunk_config.json in your home-dir, for details see https://www.npmjs.com/package/home-dir