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

solfate

v0.3.1

Published

Developer utility for building Solana programs

Downloads

13

Readme

Solfate CLI

Developer utility for building Solana programs

Setup and Install

Install the Solfate CLI from the NPM package registry:

npm i -g solfate

Prerequisites

The Solfate CLI requires the following tools/programs to already be installed:

Configuration file

The Solfate CLI supports loading a user define solfate.config.js file from inside your project's repo/working directory.

An example config file can be located here in this repo: solfate.config.js

Locating the config file

The Solfate CLI will attempt to locate and resolve the solfate.config.js file in the following manner:

  1. checking your current working directory (aka the directory your terminal is running the solfate command from)
  2. crawling up a set max number of directories (currently MAX_CRAWL_DEPTH=5)
  3. stopping when the config file (or a .git directory) is located (usually .git signifying the root of your repo)

Commands

hot :: hot reloading

Hot reload (aka auto rebuild) a Solana program on every file change to the program directory.

solfate hot [path]

Arguments

path (optional) - relative or absolute path to the root of the Solana program

Default: ./program - resolved to the current working directory

Arguments

-d (optional) - (localnet only) auto deploy the program after each successful build

NOTE: When auto deploys are enabled, the CLI will also request periodic SOL airdrops to keep your balance high enough to continue to deploy your program.

set :: set Solana network settings

Set Solana CLI network settings, either by a network "personality" name or individually setting records

solfate set [network]

NOTE: Either a network personality name, or at least one individual setting option is required to use set

Arguments

network (optional) - name of the network "personality" to set as your Solana config settings

Options

--endpoint - Solana RPC endpoint URL

--keypair - file path to the wallet keypair file

--file - file path to the Solana config file

--commitment - Solana network commitment level

--ws - websocket URL for the Solana cluster (usually auto computed when updating the endpoint

build :: build Solana program

Locally buld your Solana program

solfate build [path]

Arguments

path (optional) - relative or absolute path to the root of the Solana program

Default: ./program - resolved to the current working directory

Arguments

-d (optional) - after a successful build, auto deploy the program to the current selected network cluster

NOTE: When auto deploys are enabled, the CLI will request SOL airdrop to keep your balance high enough to continue to deploy your program.