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

pp-wapi

v0.4.3

Published

A wordpress api client

Downloads

22

Readme

A Wordpress api client

Description

A very simple Javascript client for accessing a Wordpress site's API
Currently only offers access to Posts and Terms following the standard schema
(very unstable)

Documentation

  1. Instantiate a WPClient instance passing in your wordpress site's url
  2. Call either WPClient::getPosts or WPClient::getTerms passing in a callback and args
  3. Receive Result<WPResponse, Err> and check with isOk / isErr or unwrap() to get value

A WPResponse contains meta data about the query as well as the received content

interface WPResponse<T> {
    meta: QueryMeta
    content: T // currently either BasicPost[] or Term[]
}

// not in all queries so possibility to be undefined, will move to Maybe<T> in the future
interface QueryMeta {
  count: number | undefined,
  totalPages: number | undefined
}

-- Notes

  • Currently getPosts and getTerms are curried
    • To call them either pass in callback then args like so:
      WPClient::getPosts(callback)(args)
    • Or save to a variable:
      const query = WPClient::getPosts(callback)
      query(args)
  • Uses fetch and promises, use polyfills if supporting legacy browsers
  • Caches fetch requests in memory during a session

-- Example

import { WPClient, unwrap } from "pp-wapi"

// Instantiate client
const client = new WPClient("www.testwp.com")

// Callback to run on request completion
const callback = result => console.log(unwrap(result))

// Post query args, see below for list of possible values
const args = {
    page: 2,
    categories: [ 1, 4 ]
}
client.getPosts(callback)(args)

-- Post Query Possible Args

interface PostQueryArgs {
  type?: string
  page?: number
  per_page?: number
  p?: number
  slug?: string
  search?: string
  after?: string
  categories?: number[]
  categories_exclude?: number[]
  tags?: number[]
  tags_exclude?: number[]
  author?: number[]
  author_exclude?: number[]
  exclude?: number[]
  include?: number[]
  offset?: number
  order?: Order
  orderby?: PostOrderBy
  status?: string
}

-- Term Query Possible Args

interface TermQueryArgs {
  type: string
  term_id?: number
  page?: number
  per_page?: number
  search?: string
  exclude?: number[]
  include?: number[]
  order?: Order
  orderby?: TermOrderBy
  hide_empty?: boolean
  parent?: number
  slug?: string
}