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

nonstop-hub-client

v0.1.0-3

Published

Library for communicating with the nonstop hub HTTP API.

Downloads

3

Readme

nonstop-hub-client

Library for communicating with the nonstop hub HTTP API.

Use

To get a configured instance of the server API, you can use one of the following approaches:

Configuration hash

See the Configuration section for a detailed explanation of the possible configuration values

// for uploading
var server = require( 'nonstop-hub-client' )( {
  host: 'my-hub',
  port: 443
} );
// uploads will be POSTed to https://my-hub:443/api/package/{package name}


// for getting package lists/downloading
var server = require( 'nonstop-hub-client' )( {
  host: 'my-hub',
  port: 443,
  project: 'test',
  owner: 'arobson',
  branch: 'master'
} );

// package lists will use the following URL (note - architecture and platform are set automatically)
// https://my-hub:443/api/package/list?project=test&owner=arobson&branch=master&platform=darwin&architecture=x64

Daedalus - Service and Configuration

This example is a bit over-simplified. See daedalus for more advanced use patterns. The point is to show how you can easily use this library in conjunction with daedalus and fount to auto-discover the nonstop-hub end point from Consul.

index.js

var daedalus = require( 'daedalus' )();
var server;

daedalus.initialize( {
  hub: {
    service: 'conitnua-hub',
    module: './hub-client.js',
    config: 'hub-client'
  }
} )
.then( function( fount ) {
  fount.resolve( 'hub', function( hub ) { server = hub; } );
} );

hub-client.js

// the format of the function returned from the module matches
// what daedalus expects
module.exports = require( 'continua-hub-client' );

Configuration

The configuration hash can contain a lot of information. Depending on your use case, the required minimum information changes to ensure proper function. Defaults are shown for most values except where noted.

{
  // required server config
  host: 'localhost',
  port: 80, // a port of 443 will turn https on

  // optional server config
  https: false,
  apiUrl: 'api', // base URL for all API routes
  packageList: 'package/list', // the URL to get a list of packages
  files: 'package', // URL segment where packages can be downloaded from
  uploads: 'package', // URL segment to upload packages to

  // optional paths
  downloads: './downloads',
  installed: './installed'

  // required package filters - no defaults provided
  project: 'test',
  owner: 'arobson',
  branch: 'master',
  
  // optional package filters - no defaults provided for these
  version: '0.1.0',
  build: #|'release',
  architecture: 'x64|x86',
  platform: 'darwin|linux|win32',
  osName: 'Windows',
  osVersion: '2012 R2'
}

Note: if you will be requesting package lists, you must provide project, owner and branch in the config. There are no defaults for these values.

Uploading Packages (cli/build agent)

The only required information can be provided via the service argument from daedalus or via the config argument.

var server = require( 'continua-hub-client' )( { host: 'my-hub', port: 80 } );

Listing and Downloading Packages (bootstrapper)

Listing and downloading require the project, owner and branch to be specified (at least). The platform and architecture are automatically populated based on the machine the code is running on.

var server = require( 'continua-hub-client' )( { 
  host: 'my-hub',
  port: 80,
  project: 'test',
  owner: 'arobson',
  branch: 'master'
} );

Server API

Once you have access to the server instance, you can find the latest package version available, download a package or upload a package.

download( target, [token|username], [password] )

Downloads the target package. You can provide either a token OR a username and password in order to authenticate with the hub service. The file will be downloaded to the path specified by the downloads property of the config hash (default is './downloads'). Returns a promise that resolves to an object with the format:

  { 
    path: /* path where the file was downloaded */, 
    installPath: /* path where packages should be unpacked */, 
    file: /* the file that was downloaded */
  }
// target - the full package name to download
// token|username - either a auth token or user name
// password - if a user name was provided, you should also provide a password to authenticate
server.download( 'test~arobson~master~0.1.0~1~darwin~any~any~x64.tar.gz', 'some-auth-token' )
  .then( function( info ) {
    // on success
  } );

getLatest( ignore, [token|username], [password] )

Gets information for the latest available package given the package properties set by config (or by the set calls). Returns a promise that resolves to a package information object with the format:

  {
    file: 'proj1~owner1~branch2~0.1.0~1~darwin~OSX~10.9.2~x64.tar.gz'
    project: 'test',
    owner: 'arobson',
    branch: 'master',
    version: '0.1.0-1',
    build: '1',
    platform: 'darwin',
    osName: 'any',
    osVersion: 'any',
    architecture: 'x64'
  }

Most likely, the property you need from this object will be the file property - supplying this to the download call will allow your application to download the latest.

// ignore - an array of versions that should be ignored when determining the latest package
// token|username - either a auth token or user name
// password - if a user name was provided, you should also provide a password to authenticate
server.getLatest( [], 'some-auth-token' )
  .then( function( latest ) {

  } );

setBranch( branch )

Filter packages by branch when getting latest.

server.setBranch( 'dev' );

setBuild( build )

Filter packages by build when getting latest. Valid build values are an existing build number or 'release' (limits packages to only official releases).

Note: Only use with a build number if you've called setVersion or provided a version via config

// only allow official releases when getting latest
server.setBuild( 'release' );

// limit to a specific build number
server.setBuild( 4 );

setOwner( owner )

Filter packages by specific owner (fork) when getting latest.

server.setOwner( 'ifandelse' );

setVersion( version )

Filter packages by version when getting latest. Valid versions are 3 part specifiers not including the build. Setting this without limiting the build to a number or 'release' will cause the newest build to be pulled for the version when getting latest.

server.setVersion( '0.1.2' )

upload( packageInfo, [token|username], [password] )

Uploads a package. PackageInfo should be the same format of the object returned from the pack library's create call. Returns a promise that resolves to the HTTP response body on success (statusCode === 200).

server.upload( info, 'someUserName', 'somePassword' )
  .then( function( response ) {
    // on success
  } );

Dependencies

This would not have been possible without several great Node modules:

  • request
  • when
  • lodash
  • mkdirp
  • debug

Dependents

The following nonstop projects rely on this library: