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

pnut-butter

v0.22.1

Published

pnut-butter.js – A modern, promise based wrapper library for the pnut.io API.

Downloads

8

Readme

pnut-butter.js

A modern, promise based wrapper library for the pnut.io API.

It is currently developed and tested on Node 8 LTS, but should work with basically any current browser supporting ES6 as well (feel free to open an issue if not), especially if you throw it in your typical Webpack/Babel/whatever toolchain.

Installation

npm install pnut-butter

Usage

Everything related to data fetching returns a Promise, which you can either use directly, with a supporting library like co or the upcoming async/await standard.

For example, to fetch the global timeline:

const pnut = require("pnut-butter");

(async () => {
  const { meta, data } = await pnut.global();
})();

Fetch a post by its ID:

const pnut = require("pnut-butter");

(async () => {
  const { meta, data } = await pnut.post(1234);
})();

Most methods allow any arbiritary, additional URL parameters that can be found in the official documentation. For example, you can use something like this:

const { meta, data } = await pnut.mentions({ beforeId: 1235 });

…to get posts in the mentions category before the specified id. We generate them dynamically and convert the parameters to snake_case automatically for you, so it doesn't matter if you write:

const { meta, data } = await pnut.global({ sinceId: 4567 });

or

const { meta, data } = await pnut.global({ since_id: 4567 });

Both versions work, it's just syntactic sugar and a matter of personal preference.

Documentation

You can find the full documentation of all methods here.

Custom requests

Pnut is a moving target, so there are still some methods missing and/or parameters that are not yet implemented. Therefor you can always fall back to a custom request with support for all HTTP verbs.

const pnut = require("pnut-butter");

(async () => {
  const { meta, data } = await pnut.custom("/posts/streams/explore/trending");

  await pnut.custom("/posts", "POST", { text: "Posting with pnut-butter!" });
  await pnut.custom("/posts/1234", "DELETE");
})();

Authentication

For everything that requires an authenticated user, you will need an access token. You can create one in the setting of your account on pnut.io under the "Develop" menu.

You can set it like this:

const pnut = require("pnut-butter");
pnut.token = ACCESS_TOKEN;

(async () => {
  const { meta, data } = await pnut.mentions("me");
})();

Please consult the pnut docs for further information about how authentication is handled in the network, how to aquire a "real" token able to authenticate multiple users and so on.

Changing profile / cover images

Uploading images is currently only supported on the client side. You can give the DOM node for an upload form containing file fields for "avatar" or "cover" as argument to the corresponding methods uploadAvatar / uploadCover.

A basic HTML form would look something like this:

<form id="avatar-form">
  <input type="file" name="avatar">
</form>

Depending on how your application is set up, an upload function looks somewhat like this:

async function upload(ev) {
  event.preventDefault();

  const form = document.querySelector("#avatar-form");
  await pnut.uploadAvatar(form);
}

Both, uploadAvatar and uploadCover will handle server side uploads in a future release.

App Streams

pnut-butter has support for creating, managing and reading app streams (you need a properly "signed" pair of Client ID and Client Secret to use this).

First, you need to request an app stream access token:

const pnut = require("pnut-butter");
(async () => {
  const { meta, data } = await pnut.requestAppAccessToken(
    YOUR_CLIENT_ID,
    YOUR_CLIENT_SECRET
  );
})();

If successful, you will get back a proper token in the response. Set it via:

pnut.token = YOUR_ACCESS_TOKEN;

Next step is to setup your app stream with up to 5 (!) options (post, bookmark, follow, mute, block, message, channel, channel_subscription, token, user) and a key name:

(async () => {
  const { meta, data } = await pnut.createStream({
    objectTypes: ["post", "bookmark", "follow"],
    key: "myfancykeyname"
  });
})();

For reading the stream, we provide a separate module you have to require, that preconfigures a web socket connection for you, where you can simply listen on the "message" event to read the stream:

const pnut = require("pnut-butter");
const AppStreamSocket = require("pnut-butter/dist/app_stream_socket");

pnut.token = "MY_VALID_ACCESS_TOKEN";
const ws = AppStreamSocket("myfancykeyname");

ws.on("open", event => {
  console.log("Opening app stream");
});

ws.on("message", event => {
  console.log(event.data);
});

ws.on("close", event => {
  console.log("Closing app stream", event.code, event.reason);
});

You can now work on the streaming data from the "message" event. Keep in mind that you might want to reconnect to the socket in case it closes on the server side.

Collaboration / Project status

Issues / Pull Requests are always welcome. If you have any questions, feel free to drop me an email or write a message on pnut.io. There are still a couple of things not implemented yet (creating and updating channels comes to mind), but should be stable and usable already.