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

@labshare/request-tracking-api

v1.20.5

Published

API's to implement request tracking

Downloads

5

Readme

Build Status semantic-release

Request Tracking Api

The purpose of this projects is to manage apis for request tracking.

Prerequisites

  1. Node.js (v8.11.2) - https://nodejs.org/en/download/
  2. npm install -g lsc
  3. Makes sure your config.json has a billing object with a key of facilityID and a value of the enviorment you will work in such as myrtb-ci
    • The facilityID's can be myrtb-ci, myrtb-qa, and myrtb

Example config.json:

{
    "storage": {
      "proxy": "auto"
    },
  "session": {
  "facilityPath":"/"
  },
    "facility": {
      "ServiceUrl": "https://example.exam.nih.gov/v3",
  "facilityPath": "/",
      "spfacility": {
        "User": "aws\\ExampleUser",
        "Password": "Password12345",
        "Strategy": "hybrid",
        "CustomStrategyPrefix": "i:0ǵ.t",
        "Site": "https://myrtb-ci-default.aws.labshare.org",
        "CustomStrategyName": "labshare"
      },
      "FacilityDB": "@labshare/spfacility",
      "Facilities": {
        "Type": "file",
        "Settings": {
          "Path": "./facilities.json"
        }
      }
    },
    "shell": {
      "LoadServices": true,
      "Auth": {
        "Url": "https://a.labshare.org/_api"
      }
    },
    "billing": {
      "facilityID": "myrtb-ci"
    }
  }

Running

To run the project, simply run the following command from the root of the repository:

$ lsc start services

Billing Api

Every endpoint other than the /billing endpoint needs this request body.

{
	"chargeList": String,
	"section":[{
		"sectionName":String,
		"listNames": [String]
	}],
	"endDate": String,
	"status": String
}

Example:

{
	"chargeList": "RTB-Charges-FY18",
	"section":[{
	 "sectionName":"myrtb-ci-bis",
	 "listNames": ["Reservations","PosterPrinter"]
	},{
	 "sectionName":"myrtb-ci-fcs",
	 "listNames": ["charges","reservations","flowjo billing"]
	}],
	"endDate": "10/31/2019",
	"status": "readytobill"
}

Note if section is an empty array it will run though all billing sections and lists.