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

bin-npkg-tekknolagi

v0.0.4

Published

NodeOS uses NPM for package management, but the `npm` command is not sufficient for proper installation of NodeOS packages. The `npkg` command handles all OS-related package management. If you're writing a NodeJS app, you will still use the `npm` command locally.

Downloads

6

Readme

NodeOS Package Manager

NodeOS uses NPM for package management, but the npm command is not sufficient for proper installation of NodeOS packages. The npkg command handles all OS-related package management. If you're writing a NodeJS app, you will still use the npm command locally.

Usage

Usage: npkg COMMAND PACKAGE

Commands:
  
  install      install package
  remove       remove package
  
  start        start service
  stop         stop service

Installing Packages

Installing via npkg install is a lot like npm install -g, except npkg only installs the package for the current user. Packages are installed to $HOME/lib/node_modules and binaries are linked to $HOME/bin. NodeOS will have a very minimal set of executables outside of $HOME/bin, thus a users command-line experience is almost completely isolated from other users on the system.

Removing a package only removes it for the current user. Packages and linked binaries are always partitioned by user, thus you do not need to be root to call npkg.

Binaries are discovered exactly like npm install via the bin key in package.json.

Starting Services

Packages can expose services as well as binaries. Calling npkg start PACKAGE is the same as calling npm start, only the stared service is run by init and daemonized.

The npkg start command can resolve both global and local packages. Local packages start with either ./ or / and are resolved as relative or absolute URLs. Global packages are resolved under $HOME/lib/node_modules.

Start a Relative Package

$ cd ~
$ npkg start ./myapp
--> starting ~/myapp
--> reading ~/myapp/package.json

Start a Global Package

$ cd ~
$ npkg start myapp
--> starting ~/lib/node_modules/myapp
--> reading ~/lib/node_modules/myapp/package.json

Programatic API

Access npkg programatically:

var npkg = require('npkg');
npkg.install(package, function(err,ok){
  // 
});
npkg.start(package, function(err,ok){
  //
});