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

resources.js

v1.3.0

Published

A javascript data transformation layer.

Downloads

956

Readme

Coverage Status Build Status

resources.js

A javascript data transformation layer.

Inspired by Laravels Eloquent API Resources.

Installation

npm i resources.js

Basic Usage

Create a resource, UserResource.js.

const Resource = require('resources.js');

class UserResource extends Resource {
  toArray() {
    return {
      id: Number(this.id),
      name: this.name,
      email: this.email,
      created_at: this.created_at,
      updated_at: this.updated_at,
    }
  }
}

module.exports = UserResource;

Create some data, maybe in index.js

const data = [{
  id: '1',
  name: 'Bob',
  email: '[email protected]',
  created_at: 'today',
  updated_at: 'today',
  posts: [{
      title: 'im cool'
    },
    {
      title: 'so cool cool'
    },
  ]
}, {
  id: '2',
  name: 'Waldo',
  email: '[email protected]',
  created_at: 'today',
  updated_at: 'today',
}];

Then you can transform a single item:

const single = new UserResource(data[0]).exec();
console.log(single);
/**
 *  { data:
      { id: 1,
        name: 'Bob',
        email: '[email protected]',
        posts:
         { data:
            [ { title: 'im cool - Title' },
              { title: 'so cool cool - Title' } ] },
        created_at: 'today',
        updated_at: 'today' } }
 */

Or all of them

const collection = UserResource.collection(data);
console.log(collection);
/**
 *  { data:
      [ { id: 1,
          name: 'Bob',
          email: '[email protected]',
          posts:
           { data:
              [ { title: 'im cool - Title' },
                { title: 'so cool cool - Title' } ] },
          created_at: 'today',
          updated_at: 'today' },
        ... ] }
 */

Advance Usage

Data wrapper

You can enable the data wrapper by passing true to the second arguement for both methods.

const single = new UserResource(data[0], true).exec();
console.log(single);
/**
 *  { id: 1,
     name: 'Bob',
     email: '[email protected]',
     created_at: 'today',
     updated_at: 'today' } }
 */

Or all of them

const collection = UserResource.collection(data, true);
console.log(collection);
/**
 *  [ { id: 1,
       name: 'Bob',
       email: '[email protected]',
       created_at: 'today',
       updated_at: 'today' },
     { id: 2,
       name: 'Waldo',
       email: '[email protected]',
       posts: { data: [] },
       created_at: 'today',
       updated_at: 'today' } ]
 */

If you pass a data key to collections you cannot disable this option.

Pagination

If you pass a data key to collections your transformation will be merged with the rest of the passed object.

Let's use a simple Paginator class.

class Paginator {
  constructor(data) {
    return {
      data,
      meta: {
        page: 1,
        total: data.length
      },
      links: {
        nextPage: '...',
        prevPage: '...'
      }
    }
  }
}

We'll return our data as data key along with other pagination information like meta and links

Now we can call collection with the paginator

const paginated = UserResource.collection(new Paginator(data));
console.log(paginated);
/**
 *  { data:
      [ { id: 1,
          name: 'Bob',
          email: '[email protected]',
          created_at: 'today',
          updated_at: 'today' },
        ...
     meta: { page: 1, total: 2 },
     links: { nextPage: '...', prevPage: '...' } },
 */

Nested Resources

Transforming nested resources is not to difficult, just create a new resource like PostResource.js

const Resource = require('resources.js');

class PostResource extends Resource {
  toArray() {
    return {
      title: `${this.title} - Title`
    }
  }
}

module.exports = PostResource;

Then modify the UserResource

class UserResource extends Resource {
  toArray() {
    return {
      id: Number(this.id),
      name: this.name,
      email: this.email,
      posts: PostResource.collection(this.posts, true),
      created_at: this.created_at,
      updated_at: this.updated_at,
    }
  }
}

Now when you do a transformation you'll see posts

/**
 *  { id: 1,
     name: 'Bob',
     email: '[email protected]',
     posts:
      { data:
         [ { title: 'im cool - Title' },
           { title: 'so cool cool - Title' } ] },
     created_at: 'today',
     updated_at: 'today' } }
 */