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

apible

v1.1.3

Published

create api services for any typed resource

Downloads

13

Readme

About Apible

Apible is a simple lib, based on axios, that performs basic http requests on REST API. To use an Apible instance, just provide a typed entity to Apible instance like below.

import { Apible } from 'apible';

type Entity = {
  name: string;
  id?: number;
};

const apible = new Apible<Entity>();

The created apible instance will provide the following methods :

An RXJS subject will also be provided. This subject, named events, will emit all interactions made by apible instance. It can be usefull to detect potential changes on the API and use some callback actions in your front-end.

getAll

Performs a GET request.

Simple use:

const response: Entity[] = await apible.getAll(`http://localhost:3000/entity`);

Add filters:

const response: Entity[] = await apible.getAll(`http://localhost:3000/entity`, {
    queryFilters : {
        name : 'nathan',
        anyKey: 'anyOtherInformation'
    }
});

Filters will be added as query params (example : 'http://localhost:3000/entity?name=nathan&anyKey=anyOtherInformation');

getOne

Performs a GET request.

Simple use:

const response: Entity = await apible.getOne(`http://localhost:3000/entity`, 1);

The entity's identifier will be added as a path parameter (example : 'http://localhost:3000/entity/1')

create

Performs a POST request.

Simple use:

const response: Entity = await apible.create(`http://localhost:3000/entity`, {name : 'nathan'});

update

Performs a PATCH request.

Simple use:

const entity: Entity = await apible.getOne(
    `http://localhost:3000/entity`, 1
);

entity.name = 'updated name';

const response: UpdateResponse = await apible.update<UpdateResponse>(
    `http://localhost:3000/entity`,
    entity
);

UpdateResponse can be anything. You can type the update response to fit the requested api.

delete

Performs a DELETE request.

Simple use:

const response: DeleteResponse = await apible.delete<DeleteResponse>(`http://localhost:3000/entity`, 1);

The entity's identifier will be added as a path parameter (example : 'http://localhost:3000/entity/1'). DeleteResponse can be anything. You can type the delete response to fit the requested api.

events

Subscribe to the events subject by using RXJS subscribe method :

apible.events.subscribe((event : ResourceInteractionEvent<Entity>) => {
    // do anything
})

Interactions are objects that give information on the action performed by the apible instance. Here is an example :

{
    type: 'delete',
    resource: {id: 1},
    metaData: ['any', 'custom', 'information']
}

type could be : 'create', 'delete', 'update' or 'get'. resource is the data you are handling. (note that for a create type, the event cannot return resource's id if it has not been specified in the created resource. Event is thrown before any API response). metaData is a string or an array of strings that you can feed when you use any of the apible methods

To specify interaction rules when you are making a request with apible, you pass an object with custom settings like below.

const createdEntity: Entity = await apible.create(
    `http://localhost:3000/entity`,
    { name: 'nathan' },
    {
        customInteractionMetaData : ['custom', 'metadata'],
        handleInteractivity: true
    }
);

Custom metadata can be use to improve events filters while subscribing to events subject. Here is an example:

import { Apible, ResourceInteractionEvent } from 'apible';
import { filter } from 'rxjs';

apible.events.pipe(filter(event => event.metaData.includes('custom'))).subscribe((event : ResourceInteractionEvent<Entity>) => {
    // do anything
});

By default create, delete and update methods emit events. But you can prevent them them from emitting anything by switching handleInteractivity to false in the methods options. for getOne and getAll, you can of course emit data by switching handleInteractivity to true, but be careful not to create infinite loops.