The node-os uses npm for package management, but the `npm` command is not sufficient for proper installation of node-os packages.
The node-os uses npm for package management,
but the npm command is not sufficient for proper installation of node-os packages.
The npkg command handles all os-related package management.
If you're writing a node.js app, you will still use the npm command locally.
Usage: npkg COMMAND TARGET
Commands
install install package TARGET from npm
run run a package in the foreground
show list installed packages
start start package TARGET via init
stop stop running package TARGET via init
list list active jobs
status list an active jobs status
config manipulate config from command line
Environment
NPKG_PORT/PORT the port used to connect to init (Default 1)
NPKG_BIND/BIND the address init has bound to (Default localhost)
$ npkg install wssh
$ wssh 192.168.0.123
$ npkg install wssh
$ npkg start wssh
FAQs
The node-os uses npm for package management, but the `npm` command is not sufficient for proper installation of node-os packages.
The npm package bin-npkg receives a total of 1 weekly downloads. As such, bin-npkg popularity was classified as not popular.
We found that bin-npkg demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.