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

minehut-file-watcher

v2.0.0

Published

Watch files locally then save them to your Minehut server automatically

Downloads

4

Readme

minehut-file-watcher

David npm npm GitHub

minehut-file-watcher is a helpful command line tool that will watch your files and automatically push them to your Minehut server when they are changed. This is great for people writing config files or scripts, as they don't have to type in their editor, copy-and-paste the content from their editor to Minehut's editor, then click Save, wait for it to upload, then reload in-game. Instead, they can just type in their editor and reload in-game. Nothing more.

Like this project? Star the repo
Found a bug, have a suggestion? Make an issue

Changes from v1

  • You provide a server name instead of server ID
  • You provide email and password instead of auth token
  • Supports session IDs (which means it actually works, as opposed to v1 which wasn't compatible with certain API changes)
    You can view the v1 README here

Getting Started

To get started run yarn global add minehut-file-watcher (or npm install -g minehut-file-watcher if you use NPM).

$ mh-watch

minehut-file-watcher

--setserver=<server name>
Set the server to push files to (persistent)

--setemail=<email address>
Set the email to use to authenticate with Minehut (persistent)

--setpassword=<password>
Set the password to use to authenticate with Minehut (persistent)

--getconfig
Get your current config. Useful for debugging.

--minehutpath=<remote path>
Set the path of the file you want to update remotely

After setting the above persistent config values, use mh-watch <file> (--minehutpath=<remote path>).

To clarify the --minehutpath option: you must provide it when you run mh-watch <file>, not before as a standalone option. For example, mh-watch --minehutpath=/plugins/Skript/scripts/myscript.sk and then mh-watch script.sk will not work. You need to do mh-watch script.sk --minehutpath=/plugins/Skript/scripts/myscript.sk.

Setup

In v1 of minehut-file-watcher, you needed to go through a convoluted process to get your auth token and server ID. v2 makes it really easy to get started because all you need to do is provide your email, password and server name, and minehut-file-watcher will handle the rest.

  • Set your Minehut account email with mh-watch [email protected]
  • Set your Minehut password with mh-watch --setpassword=minehutisfree78
  • Choose your server with mh-watch --setserver=MyServer (the command should output the server ID if it was successful)

After setting the three config values, run the following command in a terminal: mh-watch --minehutpath=path/to/file/on/minehut.yml path/to/my/file.yml. If I was editing a script, I would use the command mh-watch --minehutpath=plugins/Skript/scripts/shop.sk shop.sk. You need to pass the --minehutpath option every time you watch a file, while the other three config options are persistent.

Note: If the value of minehutpath is a path to a nonexistent file, the file will automatically be created on the server.