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 🙏

© 2026 – Pkg Stats / Ryan Hefner

podio-fetch

v3.0.0

Published

Low-level function for making HTTPS requests to the Podio API. See [podio-client](https://www.npmjs.com/package/podio-client) for a higher level interface.

Downloads

25

Readme

Podio fetch

Low-level function for making HTTPS requests to the Podio API. See podio-client for a higher level interface.

const fetch = require('podio-fetch')

fetch({
  fetch = globalThis.fetch,
  log = () => {},
  host = 'https://api.podio.com',
  method = 'GET',
  token,
  path,
  query,

  // one of
  form,
  json,
})

Errors

Some errors are recognized and translated into the following error classes:

TokenExpiredError
RateLimitError
UnexpectedHttpStatusError
UnexpectedHttpContentTypeError
InvalidJsonBodyError

All of the above will have a .response containing the original Request and a .body holding either parsed JSON or text depending on what was possible.

Apart from the above, errors may arise from the underlying engine. For the built-in fetch in Node.js they can be distinguished by .cause.code and include:

ECONNRESET
ENOTFOUND
ETIMEDOUT
ECONNREFUSED
EHOSTUNREACH
EPIPE
EAI_AGAIN

Formatting

const {formatPeriod} = require('podio-fetch')
formatPeriod(
  start, // Required. Date object
  end, // Optional. Date object
  utc // Optional, Boolean, defaults to `false`. Set to `true` if the date should be converted to UTC
)
// → {start: 'YYYY-MM-DD HH:MM:SS'} OR {start: 'YYYY-MM-DD HH:MM:SS', end: 'YYYY-MM-DD HH:MM:SS'}

Podio converts the dates based on the authenticated user making the request:

  • If authenticated as a User, the dates will be converted to UTC by Podio (from timezone in the users settings).
  • If authenticated as an App, the dates will be treated as UTC (in this case you should set utc param to true).