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

@diggithy/sdk

v2.0.0

Published

SDK for DIGGITHY integration

Downloads

6

Readme

DIGGITHY SDK Commitizen friendly semantic-release Lint, build, test, publish npm (scoped)

DIGGITHY SDK aims to make integration with DIGGITHY easy.

Installation

npm install @diggithy/sdk

Usage

Authorization

In order to work with the public API, you will need an API key for the instance you are managing. After you obtained the API key, there are two ways to provide the API key to the SDK.

Using environment variables

When importing the SDK it will automatically initialize using DIGGITHY_API_KEY if it is set.

Using Diggithy.Auth.init()

If you prefer not to use environment variables as described above, you can manually initialize the SDK like so:

import { Diggithy } from "@diggithy/sdk"

Diggithy.Auth.init(yourApiKeyHere);

Diggithy.Auth.init() overrides the API key that might be set using the environment variable.

Managing tickets

Creating tickets

Creating amount tickets works like this:

import { Diggithy } from "@diggithy/sdk"

Diggithy.Tickets.createTickets(amount);

The call will return a promise that resolves with a list of the UUIDs of the created tickets.

Users can then log in with their tickets when they navigate to https://<yourDiggithyInstance>/ticket/<ticketUuid>.

Deleting tickets

Deleting existing tickets works like this:

import { Diggithy } from "@diggithy/sdk"

Diggithy.Tickets.deleteTickets(["ticketUuid1", "ticketUuid2"]);

The call will return a promise that resolves with true if at least one of the tickets was deleted successfully and with false if no ticket was deleted or the list was empty.

Contributions

Contributions are very welcome! Please see our contribution guide for more information.