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

@yuetloo/metadata-composer

v1.0.18

Published

A library to manage project metadata

Downloads

4

Readme

Metadata Composer

A library that merges metadata from subgraphs indexing different networks. The interface of this library is closely similar to the theGraph interface (i.e. input/output) so that if dApps needs metadata from one network, it can simply use theGraph api with minimal changes.

Usage

import { MetadataComposer } from '@clrfund/metadata-composer'

const urls = ['https://api.thegraph.com/subgraphs/name/yuetloo/metadata-rinkeby']
const composer = new MetadataComposer(urls)

const query = '{ metadataEntries{id} }'
const { data, error } = await composer.query(query)
if( data } {
  console.log(data)
  //    {
  //      metadataEntries: [
  //        {
  //          __typename: 'MetadataEntry',
  //          id: 'rinkeby-0x123...456-59'
  //        }
  //      ]
  //    }
  //
}

if( error ) {
  console.log(error)
  //  [
  //    CombinedError {
  //      name: 'CombinedError',
  //      message: '[GraphQL] No value provided for required argument: `id`',
  //      graphQLErrors: [
  //         GraphQLError: No value provided for required argument: `id`
  //        ... stack trace ...
  //      ]
  //      networkError: undefined,
  //      response: Response {
  //         url: 'https://api.thegraph.com/subgraphs/name/...',
  //         status: 200,
  //         statusText: 'OK',
  //         headers: [Headers]
  //         counter: 0
  //      }
  //   }
  // ]
  //
}

Limitations

Currently, this library only merges the results without sorting or refining the paging according to the query request.

Sorting could be adding later to only sort the data if the orderBy fields are returned as part of the results; unlike subgraph queries which can order fields that are not in the query result.

Paging may not be implemented in this library due to performance impact.