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

@drovp/run

v4.0.0

Published

Execute one or multiple console commands on dropped items.

Downloads

23

Readme

@drovp/run

Drovp plugin to execute one or a series of console commands on dropped items.

Features:

  • Powerful command templating using JavaScript template literals.
  • Ability to set current working directory per command (supports templates).
  • Generate output items after commands have completed (more templates).
  • All templates have access to stdouts of previous commands.

Templates

Templates are JavaScript template literals allowing embedded expressions.

All variables and utilities available in templates are documented in profile's instructions.

Examples

Basic command template using a variable and a utility call:

binary-name "${path}" --param ${uid(5)}

You can use new lines and indentation to visually separate parameters, they'll be removed when expanding the template:

binary-name "${path}"
  --param ${uid(5)}
  --param2 ${Time(starttime).format(YYYY)}

New line terminal escapes \ and ^ are also supported, so you can just paste in already existing commands.


Expressions are powerful:

binary-name
  "${stdout.match(/^\[path\]([^\n]+)$/m)[1].trim()}"
  --param "${filename.toUpperCase()}"

stdout is a reference to the stdout output of the previous command. Other stdouts are available on the stdouts[] array. In the example above, we are using regular expression to extract path from an stdout line such as [path] /path/to/file to use in the current command.


You can enable bulked mode to group all items dropped into the profile into a single operation.

Default behavior is to split all dropped items into separate operations.

These items will then be available inside templates on the inputs[] array, which can then be used to do stuff like concatenating dropped files using ffmpeg:

ffmpeg
	-i "concat:${inputs.map(f => f.basename).join('|')}"
	-codec copy
	"${inputs[0].filename}-concat.${inputs[0].ext}"

Example above requires command CWD to be set to ${commondir}.