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

@patdx/run

v0.2.0

Published

This is a tool to run some script/command.

Downloads

1

Readme

@patdx/run

This is a tool to run some script/command.

Latest compiled code previewable at: https://patdx-run.now.sh

The goal is to have a command runner that is easy to integrate into various build scripts, and automatically have nice CLI output (including prefixing, line wrapping), and automatically have nice text file output, without having to worry about Node streams, etc.

It's inspired by some difficulties I've had using Cordova CLI, sometimes it's hard to find or detect an install error, I'd like to improve the quality and detail of the logging so I can recognize and highlight errors/warnings.

It's still in progress, but at the moment, it can wrap the output to the available space and preserve colors, etc.

stderr: Debugger listening on
stderr↳ ws://localhost:50312/
stderr↳ 3213da2c-e2ee-42ca-b9
stderr↳ e1-de7aa3e7793c
stderr: Debugger listening on
stderr↳ ws://localhost:50313/
stderr↳ 3213da2c-e2ee-42ca-b9
stderr↳ e1-de7aa3e7793c
stderr: For help, see:
stderr↳ https://nodejs.org/en
stderr↳ /docs/inspector
stdout: one line
stdout: reall long reall
stdout↳ reall sldkfjsd
stdout↳ lkjsdlkj fslkfklj
stdout↳ slkdjsdf lkjdfj
stdout↳ skldjf sljd
stdout: reall long this part
stdout↳ is red this part is
stdout↳ red this part is red
stdout↳ sldkfjsd lkjsdlkj
stdout↳ fslkfklj slkdjsdf
stdout↳ lkjdfj skldjf sljd
stdout:
stdout: one line
stdout: two line
stdout: three line
stdout:
stderr: stderr line

Architecture

  • Written in TypeScript.
  • Using execa to handle the command running, because that is a nice, well-supported wrapper Node's exec functionality with detailed error messages, etc.
  • Using microbundle to bundle all dependencies together so the final package has no dependencies (except Node).
  • A UMD build is also included, but it's up to the user to provide all of the required Node libraries in this case.

Some other ideas I'd like to explore:

  • handle the output in node-pty to sent window width info directly to the command being executed
  • integrate with react-ink for layout
  • make it easier to output to console and file at the same time
  • support prefixed and non-prefixed modes
  • later: Extend this runner to wrap around the cordova cli and other deploy scripts