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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@megawubs/avid

v1.0.0-beta.2.2.1

Published

API consumption on fire, inspired by Laravel's Eloquent

Downloads

44

Readme

Avid

API consumption on fire, inspired by Laravel's Eloquent

Installation

For now, this module only works inside a laravel installation.

$ yarn install @megawubs/avid

Usage

This wrapper expects a certain api design. The name of the model you create is automatically mapped to an api endpoint. Let's say we have a User model, by default Avid will generate a resource uri of /api/v1/user, expecting an json array of all user objects

A Avid model is defined like this:

import {Avid} from "@megawubs/avid"

export class User extends Avid{
    get _version(){
        return 'v1'
    }
    
    get _name(){
        return 'user'
    }
    
    posts(){
        return this.hasMany(Post, 'posts');
    }
}

export class Post extends Avid{
    get _version(){
        return 'v1'
    }
    
    get _name(){
        return 'post'
    }

    user(){
        return this.belongsTo(User);
    }
}

User.find(1) //model fetched from api
.then(user => user.posts) //fetch relations from api
.then(posts => console.log(posts)); //log relations

Post.find(1) //model fetched from api
.then(post => post.user) //fetch relation from api
.then(post => console.log(post)); //log relation

 let user = new User(); //new up a user

user.name = 'John'
user.email = '[email protected]'
user.email = 'secret'
 user.save()
 .then(user => console.log(user.id)); //1 (saved user through the API)

 User.find(1).then(user => {
 user.name = 'jane'
 user.email = '[email protected]'
 return user.save();
 }).then(updatedUser => console.log(updatedUser.name)); //jane

Testing

To run the tests you need to have docker and docker-compose installed. When you have both run docker-compose up in the project root and navigate your browser to http://localhost:8001 to run and see the tests