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

react-connect-rest

v0.11.1

Published

Type safe way of connecting React components to REST endpoints

Downloads

17

Readme

An experimental and WIP approach to a type safe and self traversing REST client.

Build Status codecov


Usage

import connectToRest, { IRestStore } from 'react-connect-rest';
import React from 'react';
import { render } from 'react-dom';

interface Foo {
  id: number;
  foo: string;
}

interface MyViewProps {
  container: IRestStore<Foo>;
}

const MyView = ({ myData }: MyViewProps) => <div>
  {myData.state.loading ? 'Loading...' : <p>
    Here is the data from the API:
    {JSON.stringify(myData.state.response)}
  </p>}
</div>;

const ConnectedView = connectToRest(MyView, { myData: '/my/api/' });

render(<ConnectedView />);

Assumptions

As mentioned, this lib has opinions about how a REST endpoint and how the data it returns looks:

  1. All entities can be uniquely identifiable by an id key.
  2. The API is self describing via HATEOAS metadata stored under a __links key.

Resolving relations via HATEOAS

import { RestStore } from 'react-connect-rest';

type Author = { id: number; name: string; }
type Book = { id: number; authors: Author[]; }

//  GET /book
//    {
//      data: [{
//        __links: [{ rel: 'authors', href: '/author/?book=1' }],
//        id: 1,
//        authors: [1]
//      }]
//    }
//
//  GET /author/?book=1
//    {
//       data: [{
//         __links: [],
//         id: 1,
//         name: 'Foo Bar'
//       }]
//    }
const bookStore = new RestStore<Book[]>('/book');

const firstBooksAuthors = bookStore.state.response.authors;

console.log(firstBooksAuthors.state.response[0].name);

Connecting multiple views to the same API

import connectToRest, { RestStore, IRestStore } from 'react-connect-rest';
import React from 'react';
import { render } from 'react-dom';


interface Foo {
  id: number;
  foo: string;
}

interface MyViewProps {
  container: IRestStore<Foo>;
}

const container = new RestStore<Foo>('/my/api/');

const MyView1 = ({ container }: MyViewProps) => null;
const MyView2 = ({ container }: MyViewProps) => null;

// We'll have a single container querying the API and multiple
// views listening to it.
const ConnectedView1 = connectToRest(MyView1, { container });
const ConnectedView2 = connectToRest(MyView2, { container });

render(<div>
  <ConnectedView1 />
  <ConnectedView2 />
</div>);

Testing

You can create stores with mocked data for use in tests:

import { RestStoreMock } from 'react-connect-rest';

interface Foo {
  id: number;
  foo: string;
}

const mock = new RestStoreMock<Foo>({ id: 1, foo: 'bar' });

console.log(mock.state.loading); // false
console.log(mock.state.response); // { id: 1, foo: 'bar' }