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

@everywhere-computer/every-cli

v0.1.2

Published

The [EveryCLI](https://github.com/everywhere-computer/every-cli) is a set of utilities for running the [Everywhere Computer](https://docs.everywhere.computer/).

Downloads

140

Readme

EveryCLI

The EveryCLI is a set of utilities for running the Everywhere Computer.

Installation

npm i -g @everywhere-computer/every-cli

Usage

Full docs can be viewed here.

Prerequisites

Create a custom TS or Wasm function(or clone TS examples repo here)

Creating the Everywhere Computer environment

To start a Homestar node, IPFS node, API gateway and Everywhere Computer control panel

every dev <PATH_TO_FUNCTION_FILE>

To create a multi-function Homestar workflow

every dev <PATH_TO_FUNCTION_FILE> <PATH_TO_OTHER_FUNCTION_FILE>

Passing your own Homestar config

By default the EveryCLI will use the default homestar.toml values to specify configuration settings for your Homestar node.

If you would like to specify your own toml file to be used as the configuration for Homestar, you can use the --config argument:

every cli dev <PATH_TO_YOUR_FUNCTION_DIR>/hello.wasm --config ../<YOUR_CONFIG_FILE_NAME>.toml

You can specify as many or as few values in your toml file as you like and the EveryCLI will prioritize the values from your config over the default values.

This means, if you only want to specify a different IPFS port, you simply need to create a toml file with

[node.network.ipfs]
port = 5002

and the EveryCLI will upload your functions to IPFS on port 5002 and configure Homestar to use IPFS port 5002, as well.

If you have specified your own config file, the control panel will run locally so its .env file can be overwritten if necessary:

✔ IPFS is running at http://127.0.0.1:5002/debug/vars
✔ Functions parsed and compiled
✔ Homestar is running at http://127.0.0.1:8020
✔ Control Panel is running at http://127.0.0.1:5178

◐ Starting cloudflared tunnel to http://127.0.0.1:3000/

... a QR code ...

➜ Local:    http://127.0.0.1:3000/
➜ Tunnel:   https://sometimes-comical-word-set.trycloudflare.com