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

taiga-njs

v0.1.2

Published

NodeJS implementation of Taiga API

Downloads

4

Readme

taiga-njs

Soon-to-be NodeJS Implementation of Taiga API

WARNING

This is in the very initial stages of this module and will change greatly. I am publishing this for my own use in other projects at this time and do not offer or provide support. Please check back in a couple weeks for a more mature offering.

UPDATE: This is STILL in extremely early stages of development, but I'm figuring out a bit more about what I want this to be ;). If you have suggestions and/or ideas, please feel free to get in contact with me (check the github profile page).

Usage

Initialization

Simply provide an API key for a new Client instance.

var taiga = require('taiga-njs');
var client = new taiga.Client("YOUR_API_KEY");

The Objects

Client : the taiga client, instantiated with your API key

Response: The response wrapper. Has the following structure (so far):

var Response = function(type, body) { 
	this.body = body; 
	this.status = "success";
	this.type = type;
};

Usage

All calls to the API will return a wrapper response object in a promise that will contain the entire response in addition to a couple key helper fields. I may change the specific structure, but the concept will likely stay unless someone poses a really clear reason why this is wrong.

#####Issues My current focus is around the Issues portion of the Taiga API. Currently, I can create a new high-priority, very sever issue :).

// taiga and client already initialized
// project id = 12345
var issue = new taiga.Issue(12345, "Issue Subject", "Issue Description");
client.createIssue(issue)
  .on("success", function(res) {
  	// do something with the response
  })
  .on("error", function(res) {
  	// handle the error
  });

... which is what I need it for right now :).