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

@transformation/process

v7.0.2

Published

Transformations for working with processes

Downloads

6,926

Readme

@transformation/process

A package for using child processes.

exec

Spawns a shell and executes the given commands. See Node child_process.spawn for more information.

import { exec } from "@transform/process";
import { concat, lines } from "@transform/stream";
import { emitItems, interleave, skipLast } from "@transform/core";
await expect(
  pipeline(
    emitItems("Hello", "beautiful", "world!"),
    interleave("\n"),
    exec(`sed 's/^/> /g' | grep -v beautiful`),
    concat()
  ),
  "to yield items",
  ["> Hello\n> world!\n"]
);

You can also pipe data into a sub-process.

await expect(
  pipeline(
    emitItems("Hello\nfantastic\nworld"),
    exec("grep -v fantastic"),
    lines()
  ),
  "to yield items",
  ["Hello", "world", ""]
);

spawn

Spawns a new sub-process. See Node child_process.spawn for more information.

import { spawn } from "@transform/process";
import { lines } from "@transform/stream";
import { pipeline, skipLast } from "@transform/core";

You can use it to emit items into the pipeline.

await expect(
  pipeline(spawn("ls", [testDir]), lines(), skipLast()),
  "to yield items",
  ["0.txt", "1.txt", "2.txt"]
);

You can also pipe data into a sub-process.

await expect(
  pipeline(
    emitItems("Hello\nfantastic\nworld"),
    spawn("grep", ["-v", "fantastic"]),
    lines(),
    skipLast()
  ),
  "to yield items",
  ["Hello", "world"]
);

Multiple sub-processes can be combined.

await expect(
  pipeline(spawn("ls", [testDir]), spawn("grep", ["0"]), lines(), skipLast()),
  "to yield items",
  ["0.txt"]
);

startProcess/childProcess

Starts a child process pipeline in a new Node instance.

const { startProcess, childProcess } = require("@transformation/process");
import { pipeline } from "@transform/core";

Notice this is only useful for cases where your pipeline is more CPU intensive than the overhead of communicating with the child process.

As an example let's try to square numbers in a child process.

We start by defining the child process pipeline (square.js).

module.exports = childProcess(map((n) => n * n));

Now we can load start the process as part of our pipeline.

await expect(
  pipeline(
    emitItems(0, 1, 2, 3, 4, 5, 6, 7, 8, 9),
    startProcess("square.js"))
  ),
  "to yield items",
  [0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
);

What is happening here, is that every item is serialized and send into the child process for processing. When the child process emits new items, they are serialized and passed back to the main pipeline.