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

ldc

v0.0.0

Published

linked data container manager

Downloads

2

Readme

ldc

ldc

Linked Data Container manager.

NPM

Usage:

##CLI

Usage: ldc <command> [options] where command is:
  - init [globs] [urls] [-d, --defaults] [-b --codebundle <relative/path/to/code/directory>] Interactively create a container.jsonld file and add the files listed as globs (*.csv ... and urls) as dataset. Be sure to double quote the glob so that the shell does not expand them
  - cat       <container name>[@<version>] [-e, --expand]
  - install   <container name 1>[@<version>] <container name 2>[@<version>] <container url> ... [-t, --top] [-a, --env] [-c, --cache] [-r, --require] [-s, --save]
  - publish
  - unpublish <container name>[@<version>]
  - adduser
  - owner <subcommand> where subcommand is:
    - ls  <container name>
    - add <user> <container name>
    - rm  <user> <container name>[@<version>]
  - search [search terms]
  - help [command]

Options:
  -f, --force       overwrite previous if exists
  -d, --defaults    bypass the promzard prompt
  -t, --top         install in the current working directory (and not within ld_containers/)
  -a, --env         install all the environment files present in the directory at publication time
  -e, --expand      expand the JSON-LD document
  -s, --save        data packages will appear in your dataDependencies
  -c, --cache       force the inlined dataset (contentData) to be stored in their own file in ld_resources/
  -b, --codebundle  treat the listed directory as a code project
  -h, --help        print usage
  -v, --version     print version number

Using ldc programaticaly

You can also use ldc programaticaly.

var Ldc = require('ldc);
var ldc = new Ldc(conf);

ldc.install(['myctnr/0.0.0', 'mydata/1.0.0', 'http://example.com/mydata'], {cache: true}, function(err, ctnrs){
//done!
});
ldc.on('log', console.log); //if you like stuff on stdout

See bin/ldc for examples.

Registry

By default, ldc uses Standard Analytics IO data registry hosted on cloudant.

License

MIT