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

autoup

v1.0.5

Published

a Hot update module,support different types of files

Downloads

4

Readme

autoup

Install

yarn add autoup -g
or
npm install autoup -g

Features

  • Support go,c,node auto reload
  • Support customize an overloaded command (configFile usage)

Example

command usage

autoup -f ./index.js -d ./src/
  • -f Represents the file that needs to be reload (must require)

  • -d Indicates the folder or directory to monitor. If -d is not present, the value of -f is monitored by default (optional)

configFile usage

  1. Frist

You need to run autoup init in the working directory to generate a configuration file for autoup

  1. Next

you could config .autoup.json,through the annotation below

{
  // Represents the file that needs to be reload
  "restartFile": "./index.js",
  // Indicates the folder or directory to monitor
  "notifyCwd": "./",
  // Delay to update
  "restartTime": 1000,
  // You can choose one from [.go .c .js] as the configuration
  "type": ".js",
  // Customize an overloaded command,If you set this, restartFile and type will be invalid
  "custom_restart_cmd": null
}
  1. Finally

You just run autoup to make it reload