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

j-dgraph

v1.1.37

Published

A quick javascript client for Dgraph without GraphQL.

Downloads

39

Readme

j-dgraph

The easy-to-use package to query dgraph without GraphQL. So far it has been tested on Angular, Angular Universal, and Sveltekit. It should, however, work in almost any javascript framework both server side and client side.

Let me know if you have problems in the issue section.

It uses GraphQL, Urql, and my easy-dgraph package under-the-hood!

Installation

npm i j-dgraph

Example 1

A basic query with headers...

import { dgraph } from 'j-dgraph';

const _dgraph = new dgraph({ 
  url: 'https://your-endpoint/graphql', 
  headers: { "X-Auth-Token": localStorage.getItem('X-Auth-Token') }
});

const { data, error } = await _dgraph.type('post').filter('0x1').query({ id: 1, name: 1 }).build();

if (error) {
  console.error(error);
}

console.log(data);

Example 2

Pretty print errors, use headers, and a custom query...

import { dgraph } from 'j-dgraph';

...

const dg = new dgraph({
    url: 'https://your-dgraph-endpoint/graphql',
    headers: async () => ({ "X-Auth-Token": await this.getToken() }),
    isDevMode: isDevMode(),
    prefix: 'blog_'
}).pretty();

const { data, error } = await dg.type('queryFeatureSortedByVotes')
      .customQuery({
        id: 1,
        name: 1,
        url: 1,
        author: { id: 1 },
        totalVotes: 1,
        description: 1,
        votes: {
          id: 1
        }
      })
      .build()

if (error) {
  console.error(error);
}

console.log(data);

Example 3

Subscriptions work out-of-the-box with error handling!

import { dgraph } from 'j-dgraph';

const _dgraph = new dgraph({ url: 'https://your-endpoint/graphql' });

const sub = _dgraph.type('post').filter('0x1').query({ id: 1, name: 1 })
  .buildSubscription()
  .subscribe(
    (snapshot: any) => {

    console.log(snapshot);

  }, (error: string) => {

    console.error(snapshot);

  });
...

onDestroy(() => 
    sub.unsubscribe();
);

Constructor Options

/**
 * @param 
 *   url - api endpoint url
 *   type? - node name
 *   isDevMode? - boolean for Developer Mode
 *   fetch? - fetch function
 *   headers? - headers function, can be async
 *   prefix? - the prefix name for the type
 */

Note: In development mode, all GraphQL queries and results are printed to the console. I have simplified all messages in DGraph to be easily readable, including errors.

You can also import the EnumType from easy-dgraph like so:

import { dgraph, EnumType } from 'j-dgraph';
  • Errors are thrown, so use try / catch blocks to catch them.
  • use .networkOnly() if you want to skip graphql caching

Every single thing you can do in Dgraph's GraphQL, you can do with no configuration with this package.

J


For All Easy-DGraph Documentation, see: dev.to: easy-dgraph

For Examples, see: Test File