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

castle-api-client

v7.0.0

Published

Castle API Client

Downloads

8,704

Readme

ghost-api-client

Ghost server API client

An API client for ghost-server

This provides a simple API client for connecting to the ghost-server server.

The main use case for it is login and identity. For that, it relies on Expo user accounts.

Reasons for having a separate server

There are two reasons to have a separate server instead of just using the www stack that we already have.

(1) Since Ghost is a new thing that needs to evolve in pretty fast moving ways to become something viable and good, we want to decouple it from the pretty big monolithic web stack that we have for www that has been around for a while.

(2) Since we want to connect to Ghost from Lua and JS, having a simple interface that is easy to talk to from each of those might be important.

Implementation

The Ghost Server is implemented using a simple JSON RPC API. This base layer is in two packages here: https://github.com/expo/thin-api

On top of that, there are two packages here under the js/ and lua/ directories that are, unsurprisingly, the JS and Lua packages.

The JS version of the client can work in pretty much any JavaScript environment including Node, the Browser, Electron, React Native.

The Lua version of the client is just designed to work under Ghost.

There is still some work to do

The Protocol

There is one endpoint, sort of like GraphQL. By default it's http://localhost:1380/api.

For now, there is a "production" version of it that is continuously deployed from master running at https://ghost-server.app.render.com/api

To make a call, you make an HTTP POST request to that URL with an application/json form body that includes a JSON object with the following fields:

  • method
  • args

In response, you'll get back a JSON object that includes these fields:

  • data
  • error
  • clientError
  • warnings
  • result
  • commands

For more info about implementing API methods, read the README in https://github.com/expo/ghost-server.