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

teamspeak-query-client

v0.1.6

Published

TeamSpeak Query Client that works

Downloads

29

Readme

teamspeak-query-client

Greenkeeper badge

Build Status codecov

A TeamSpeak Query Client that works.

Example

const query = new Query({ //you can also leave this blank, then it connects to localhost:10011
  host: "yourserver.de",
  port: 10011
})
query.connect(err => {
  if (err) throw err //Likely connection refused
  query.login("serveradmin", "mysecretpw", err => { //you can also skip login to opperate as guest query
    if (err && err.id === 520) throw new Error("Invalid Password")
    if (err) throw err //something weird happened
    query.cmd("use", 1, err => { //this is easy and works.
      if (err) throw err //likely no permissions
      query.list("clientlist", ["-uid"], (err, res) => { // "list" ensures res is an array at all time
        if (err) throw err //likely no permissions
        console.log(res)
      })
    })

    query.cmd("servernotifyregister", { event: "server" }, err => { //subscribe to "server" events
      if (err) {
        throw err
      } else {
        query.on("cliententerview", console.log) //user has joined
        query.on("clientleftview", console.log) //user has left
        query.on("notify", console.log) //all the events
      }
    })
  })
})

There are hundreds of ts3 clients. Why write yet another one?

I've seen many ts3 querys for nodeJS. Every client had it's own flaws.

Some didn't even really work, some had trouble dealing with more than one server.

So I've written mine in the hope it works