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

valence-devtools

v0.4.0

Published

Signature tools for Valence projects

Downloads

7

Readme

Valence Dev Tools

Support on Patreon npm version

Developer tools for Valence projects.

Installing Valence Dev Tools

npm install -g valence-devtools

Using Valence Dev Tools

Setup

First, you'll need to setup your access token for a Valence Update Server.

Once you have a token from the server, run this command to configure it locally:

covalence token replaceThisStringWithTheToken

Key Management

Next, you're going to need a keypair. Keypairs consist of a signing key (also known as a "private key" or "secret key" in cryptography), and a verification key (also known as a "public key").

covalence keygen

By default, this will only generate a keypair and store it locally.

The default behavior was chosen so that, if you would like to generate your signing keys offline and then shepherd the verification key to an Internet-connected computer, you can.

Run covalence export FILENAME to get the verification key, and covalence associate FILENAME it with your publisher account. These commands do not need to be run on the same machine, but the file created by the export command is necessary for the associate command.

You may also run covalence backup and covalence restore to make copies of your signing keys.

Command Line Interface

init (covalence init)

Creates an empty valence.json file. Useful for converting existing Electron apps to use the Valence auto-update framework.

begin (covalence begin)

Run this whenever you want to start building a new release.

since (covalence since TAG)

Adds all of the files changed since a particular git tag. Useful for quickly creating a release file.

add (covalence add FILE)

Run this command to add a file to the release package.

ship (covalence ship VERSION CHANNEL)

Builds, signs, and uploads your package. Note that this can be broken up into separate atomic steps:

  1. covalence package
  2. covalence sign path/to/package.zip
  3. covalence upload VERSION CHANNEL