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

@windmill-labs/hub-cli

v1.0.5

Published

Windmill hub CLI

Downloads

11

Readme

Hub CLI

Setup

You can run it directly with bunx @windmill-labs/hub-cli or install it globally with npm install -g @windmill-labs/hub-cli in which case you can run it with wmill-hub.

Create a .env file in the root of the project with the following content:

# url of your private hub
HUB_URL=https://hub.my.url 

# to get a token, create a token for a superadmin user on your **Windmill instance**.
TOKEN=your_token 

Sync from private Hub

To sync from a private hub, run the following command:

wmill-hub pull

This will pull all the scripts from the private hub and save them in the hub folder.

Sync to private Hub

After editing your scripts, run the following command to push the changes to the private hub:

wmill-hub push

Create a new script locally

To create a new script locally, run the following command:

wmill-hub create --summary "My script summary" --language bun --kind action --app my_integration

or simply:

wmill-hub create -s "My script summary" -a my_integration

Language and kind are optional, they default to bun and action respectively.

You can then edit the script in the hub folder. Once you are done, you can push it to the private hub using the wmill-hub push command.

Sync from the official Hub

To sync from the official hub, run the following command:

wmill-hub wm-pull

You can then run wmill-hub push to push the scripts to your private hub. If you don't want all of them, delete the integrations you don't want before the first push. If you want to modify them, do it directly on the hub, not in the hub folder. To get the latest version of the official hub, run wmill-hub wm-pull again. It will not overwrite the imported scripts you modified on the hub.