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

ulixee

v0.0.1

Published

- Step 1: - npm install -g @ulixee/cli - Step 2: - ulixee start - You’ll be prompted to create a keypair and lockfile. These both need to go into your deployment/project. - Step 3: - Search for schemas at https://ulixee.network (ask for credenti

Downloads

7

Readme

#Install the Ulixee CLI and your Schema(s)

  • Step 1:
    • npm install -g @ulixee/cli
  • Step 2:
    • ulixee start
      • You’ll be prompted to create a keypair and lockfile. These both need to go into your deployment/project.
  • Step 3:
    • Search for schemas at https://ulixee.network (ask for credentials)

#Add the Ulixee Client to your Project

  • npm install —save @ulixee/client
    • Run this in your project
    • NOTE: your lockfile and keyfile need to be deployed with your app. Include in your deployment/project

#Start Querying for Data

  • Write your queries into your app. Your data type has the available fields to retrieve and the parameters to retrieve data.

    • NOTE: you can also find documentation here: https://ulixee.network (ask for credentials)
  • For each query, you will specify a “view of truth”. For example, RestaurantReservations might support opentable.com, reserve.com and a few others.

    • You can explore which views of truth are supported using the cli (“find schemas” menu option)
    • You can also find supported views of truth for a schema on https://ulixee.network (ask for credentials)
  • Query formats look a form of GraphQL.

    • The fist parameter to a query is the Schema name (can be found in your ulixee-lock.json file if you forget).
    • Following your lock file are the filter parameters in parentheses. Multiple parameters should be comma separated
    • The fields parameter looks like a graphql set of parameters for ease of use.
    const Ulixee = require('@ulixee/client');
    
         (async function run() {
           try {
             const ulixee = new Ulixee({ lockfile: 'ulixee-lock.json' });
             const request = await ulixee.get('EncyclopediaEntry (name: Blockchain, page: 1)', {
               fields: `
                 title
                 url
                 extract
                 contributors {
                   username
                 }
               `,
               viewOfTruth: 'wikipedia.com',
               maxTimeInCache: '10s'
             });
    
             console.log(JSON.stringify(request, null, 2));
           } catch (err) {
             console.log(err);
           }
         })();