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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@vqueue/sdk

v0.1.6

Published

A toolset for Virtual Queue integrations in Node.js

Readme

Virtual Queue Node.js SDK

A toolset for Virtual Queue integrations in Node.js

Installation

You can install the SDK from the npm package @vqueue/sdk

npm i @vqueue/sdk

How to use

[!NOTE] See examples for more

You can verify the token with the function verifyToken as shown in this example within an Express app

import express, { Request, Response } from 'express'
import { verifyToken } from '@vqueue/sdk'

const app = express()

const port = process.env.PORT || 3000

// Verify the token at root path, this expects a `token` url query param
app.get('/', (req: Request, res: Response) => {
  const token = req.query.token as string

  // Call `verifyToken`
  verifyToken(token)
    // If there is no problem with the API request
    // you get a `VerificationResult` that tells you
    // if the token is valid or not
    .then((verificationResult) => {
      res.json(verificationResult)
      // Here you can handle your business logic discriminating
      // by the `verificationResult.success` boolean value
    })
    // In case of errors like network errorr, invalid UUID
    // or any unexpected results you'll get an exception
    //
    // If you prefer you can use the `safeVerifyToken` function
    // that never throws but returns {succes: false,
    // message: <exception message>} in case of unexpected errors
    .catch((err) => {
      console.log(err)
      res.json({
        error: 'There was an error while verifying the token',
        exception_message: err,
      })
    })
})

app.listen(port, () => {
  console.log(`The server is running at http://localhost:${port}`)
})