@berty/cli NPM package
A simple Node wrapper around berty. It fetches the right berty executable before piping all provided command line arguments to it.
$ node_modules/.bin/berty -h
INFO berty not found. Attempting to fetch it...
INFO fetched berty v2.364.5
INFO extracting archive...
INFO berty available, let's go!
USAGE
berty [global flags] <subcommand> [flags] [args...]
SUBCOMMANDS
daemon start a full Berty instance (Berty Protocol + Berty Messenger)
...
If you want to download a specific berty version, you can set BERTY_VERSION env before you run the command.
$ BERTY_VERSION=2.364.5 npx @berty/cli version
Add to your build scripts in package.json to build you site from NodeJS:
...
"scripts": {
"berty-daemon": "berty account-daemon -node.account.listeners /ip4/127.0.0.1/tcp/9092/grpcws -node.listeners /ip4/127.0.0.1/tcp/9091/grpcws --log.filters=bty.grpc"
},
"dependencies": {
"@berty/cli": "*"
},
...
Execute directly via npx:
npx @berty/cli daemon
based on https://github.com/nikku/hugo-cli by Nico Rehwaldt
MIT
FAQs
A node friendly wrapper around berty (https://berty.tech/)
We found that @berty/cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.