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

lawnman

v0.2.1

Published

The one that maintains the development lawn

Downloads

7

Readme

lawnman

Keeps the lawn clean

lawnman runs your npm scripts on changes. Uses nodemon and npm-run-all.

Inspired by yardman.

Install

npm i lawnman -D

Then use lawnman in your package.json scripts:

{
  "scripts": {
    "dev": "lawnman js,json lint test",
    "lint": "eslint lib/ --fix",
    "test": "ava"
  }
}

Usage

lawnman <ext>[,<ext>,...] <script> [<script...>]\
  --and\
  <ext>[,<ext>,...] <script> [<script...>]\
  --and\
  ...

Examples

Run the test script when any js file change.

lawnman js test

Watch js and scss files and compile accordingly

  • Runs npm run babel when any js file changes
  • Runs npm run compass when any scss or png file changes
lawnman js babel --and scss,png compass

Watch js files and run multiple npm scripts
Runs npm run test and then npm run format when any js files change

lawnman js test format

.lawnmanrc

If you only have one script in package.json that uses lawnman, you can put the arguments into a .lawnmanrc file.

For example, if you have this script in your package.json

{
  "scripts": {
    "dev": "lawnman cpp,cc,h,hpp,gyp rebuild e2e --and js,json lint test --and scss compass",
    "test": "...", ...
  }
}

You can put the arguments into a .lawnmanrc file to clean up your package.json to have it only run lawnman. Empty lines is like --and in the command line. It also supports comments.

# Build addons and run end-to-end tests
cpp,cc,h,hpp,gyp rebuild e2e

# Lint and test javascript
js,json lint test

# Compile scss
scss compass

Your dev script will then look much nicer

{
  "scripts": {
    "dev": "lawnman",
    "test": "...", ...
  }
}