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

files-pipeline

v0.0.4

Published

🧪 Pipeline for files.

Downloads

276

Readme

files-pipeline 🧪

Installation

First, install the files-pipeline component like so:

npm install -D -E files-pipeline

Then, create a new pipeline from this component:

index.ts

import { files } from "files-pipeline";

await new files().in("./input");

Getting started

The pipeline will now provide you with a process method which you can use to call the callback on each file from the pipeline.

index.ts

import { files } from "files-pipeline";

await (
	await (await new files().in("./input")).by("**/*.md")
).pipeline({
	// Prepend some content to all of the text files
	wrote: (ongoing) => (ongoing.buffer += "LICENSE [MIT]"),
});

These are the defaults for each callback.

import { files } from "files-pipeline";

await new files().pipeline({
	wrote: async (ongoing) => ongoing.buffer,
	read: async (ongoing) =>
		await fs.promises.readFile(ongoing.inputPath, "utf-8"),
	passed: async () => true,
	failed: async (inputPath) => `Error: Cannot process file ${inputPath}!`,
	accomplished: async (ongoing) =>
		`Processed ${ongoing.inputPath} in ${ongoing.outputPath}.`,
	fulfilled: async (plan) =>
		`Successfully processed a total of ${plan.files} ${
			plan.files === 1 ? "file" : "files"
		}.`,
	changed: async (plan) => plan,
});

You can add multiple paths to your pipeline by specifying an array as the path variable.

index.ts

import { files } from "files-pipeline";

await new files().in(["./input", "./input2"]);

You can also provide a map of paths for different input output directories.

index.ts

import { files } from "files-pipeline";

new files().in([new Map([["./input", "./output"]])]);

You can provide a filter to exclude files from your pipeline. A filter can be an array of regexes or a single match. You can use functions, as well to match on file names.

index.ts

import { files } from "files-pipeline";

await new files().not([
	"my-awesome.file",
	(file: string) => file === "./input/this-file-will-not-be-processed.txt",
]);

Set logger to 0 if you do not want to see debug messages. Default is 2.

index.ts

import { files } from "files-pipeline";

new files(0);

Changelog

See CHANGELOG.md for a history of changes to this component.

Lightrix logo