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

rest-fetch

v0.2.1

Published

a library to fetch graph of rest resources

Readme

A annotations based typescript library, to fetch graph of objects, exposed as rest/HATEOAS resources.

tutorial

Suppose we have 2 resources, persons and cities, and persons has a subresource address:

GET /persons/pippo
{
  "name" : "pippo",
  "friends" : [
    "/persons/minni"
  ],
  "address" : "/persons/pippo/address"
}
GET /cities/RE
{
  "name" : "RE"
}
GET /persons/pippo/address
{
  "street" : "dei pomi",
  "city" : "/cities/RE"
}

and we want to map those resources to the typescript model:

interface City {
  name:string
}

interface Address {
  street:string
  city:City
}

interface Person {
  name:string
  friends:Person[]
  address:Address
}

We can achieve the result defining few classes:

import {link, fetch} from "rest-fetch"

class CityImpl implements City {
  name:string
}

class AddressImpl implements Address {
  street:string
  
  @link()
  city:City
}

class PersonImpl implements Person {
  name:string
  
  @link({ arrayOf:Person })
  friends:Person[]
  
  @link()
  address:Address
}

And then:

const result:Promise<Person> = fetch(PersonImpl).from("/persons/pippo")  

See tests for more examples

It also works for cyclic/recursive structures.

Issues/Limitations

  • classes instantiation is done invoking the constructor with no arguments
  • @link() and @convert() annotations can be specified only for properties of classes
  • class declaration order matters, actually you can only reference a previously defined class in link, or convert annotations