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

dirbuild

v0.5.5

Published

A bit like Make but for directories

Downloads

15

Readme

dirbuild

A bit like Make but for directories

The idea

Make works really well with file in, file out processes, but breaks down when you have directory in, directory out processes. This aim to handle that.

The dirbuild config file defines some targets (a lot like with make), where each target has:

  • a command
  • some glob patterns to capture which files affect the outcome of that command
  • the path to the directory that command creates

Then, when running a target with dirbuild [mytarget] (target is optional, defaults to the first target in the config file), that target is found in the config file, the dependencies are resolved and each file is hashed. The output directory is checked for a manifest file, if it exists with the same hashes for each file, then nothing to do. Otherwise, runs the command, then writes the manifest file.

The config file

Named .dirbuild.yml.

targets:
  mytarget:
    command: npm run build
    depends:
      - '*.txt'  # every .txt file in the current directory
      - '**/*.js'  # every .js file in any subdirectory
      - package.json
    dependsExclude:
      - node_modules/**  # ignore everything in node_modules
    output: build/

The manifest file

Generated by dirbuild, and stored in the output directory once the command completes at [outputDirectory]/.dirbuildManifest.yml.