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

npm-list-author-packages

v2.0.1

Published

List an author's packages.

Downloads

46

Readme

Author Packages

NPM version Build Status Coverage Status Dependencies

List an author's packages.

Installation

$ npm install npm-list-author-packages

Usage

var ls = require( 'npm-list-author-packages' );

ls( options, clbk )

List an author's packages.

ls( {'username': '<username>'}, clbk );

function clbk( error, list ) {
	if ( error ) {
		throw error;
	}
	console.log( list );
	// returns ['<pkg1>','<pkg2>',...]
}

The function accepts the following options:

  • username: author username (required).
  • registry: registry. Default: 'registry.npmjs.org'.
  • port: registry port. Default: 443 (HTTPS) or 80 (HTTP).
  • protocol: registry protocol. Default: 'https'.

To query an alternative registry, set the relevant options.

var opts = {
	'username': '<username>',
	'registry': 'my.favorite.npm/registry',
	'port': 8080,
	'protocol': 'http'
};

ls( opts, clbk );

ls.factory( options, clbk )

Creates a reusable function.

var get = ls.factory( {'username': '<username>'}, clbk );

get();
get();
get();
// ...

The factory method accepts the same options as ls().

Notes

  • When querying the main registry, the function only returns non-scoped public packages (see NPM issue #8244).

Examples

var ls = require( 'npm-list-author-packages' );

var opts = {
	'username': 'kgryte'
};

ls( opts, clbk );

function clbk( error, list ) {
	if ( error ) {
		throw error;
	}
	console.log( list );
	// returns ['<pkg1>','<pkg2>',...]
}

To run the example code from the top-level application directory,

$ DEBUG=* node ./examples/index.js

CLI

Installation

To use the module as a general utility, install the module globally

$ npm install -g npm-list-author-packages

Usage

Usage: listpkgs [options] user

Options:

  -h,  --help                Print this message.
  -V,  --version             Print the package version.
  -p,  --port port           Registry port. Default: 443 (HTTPS) or 80 (HTTP).
       --registry registry   Registry. Default: 'registry.npmjs.org'.
       --protocol protocol   Registry protocol. Default: 'http'.

Notes

  • The package list is written to stdout as a newline-delimited string.

Examples

$ DEBUG=* listpkgs kgryte
# app-boot
# app-etc
# app-etc-config
# ...

Tests

Unit

This repository uses tape for unit tests. To run the tests, execute the following command in the top-level application directory:

$ make test

All new feature development should have corresponding unit tests to validate correct functionality.

Test Coverage

This repository uses Istanbul as its code coverage tool. To generate a test coverage report, execute the following command in the top-level application directory:

$ make test-cov

Istanbul creates a ./reports/coverage directory. To access an HTML version of the report,

$ make view-cov

Browser Support

This repository uses Testling for browser testing. To run the tests in a (headless) local web browser, execute the following command in the top-level application directory:

$ make test-browsers

To view the tests in a local web browser,

$ make view-browser-tests

License

MIT license.

Copyright

Copyright © 2015. Athan Reines.