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

@utilx/process

v0.0.9

Published

Downloads

3

Readme

process-utils

import r from "process-utils"

async function main(){
    const { code, stdout, stderr } = await r("echo hi")
    if (code === 0) console.log(stdout)

    r$("echo hi")
    r$.ctx.code = 0
    console.log(ctx.pid, ctx.status)
    
    const p = await ra("echo hi")
    r("echo hi")

    await npm.install.save_dev("fs-extra", "numpy")
    
    npm.install.save_dev$("fs-extra", "numpy")

    r$("apt install ")

    r$("apt install vim emacs -y")
    r$("brew install markdown")
    r$("yum install vim -y")

    const { error, pid, status, code, signal } = await npm.install.save("fs-extra")
    const { error, pid. status, code, signal } = npm.install.save$("fs-extra")
    const npm_res = await npm.install("fs-extra")

    npm.install.save$("fs-extra").pipe( awk.check$("") )

    const p1 = await npm.install.save$("fs-extra").throwError()
    npm.install.save("fs-extra")

    console.log(npm_res.pid, npm_res.status)

    apt.install.yes$("vim")
    console.log(ctx.pid, ctx.status)

    await apt.install("vim")
    console.log("visualized")

    apt.install_("vim")
    apt.install("vim").toString_() // promise design

    apt.install("vim") // promise design

}

关于result的设计,我们默认需要用户写防御式代码

const result = processinstance.get()
"code" in result && console.log(result.code)
if ("code" in result) {
    console.log(result.code, result.signal)
}

另外一种写法是,用户很确定这里不会有问题,否则程序会以ERROR方式中断

const result = processinstance.getOrThrow() // no Error
console.log(result.code, result.signal)