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 🙏

© 2026 – Pkg Stats / Ryan Hefner

bolt-uxp-utils

v1.3.6

Published

Utils library to build UXP plugins for Premiere Pro and Photoshop

Readme

bolt-uxp-utils

A helper library for building UXP plugins for Adobe Premiere Pro and Photoshop.

Status

Active development. Current helper count:

  • Premiere Pro - 34 helpers
  • Photoshop - 3 helpers

Pick your path

There are two ways to use this library, depending on how your plugin is built:

| Your plugin uses… | Use this path | | ------------------------------------------------------------ | ------------------------------------------------------------ | | A bundler (Bolt UXP, Vite, Webpack, esbuild, etc.) | Path A - with a bundler | | Plain UXP plugin created with UXP Developer Tool, no bundler | Path B - without a bundler |

Not sure? If you have a vite.config.ts, webpack.config.js, or your project was created with Bolt UXP, you're on Path A. Otherwise you're on Path B.


Path A - with a bundler

Install

npm install bolt-uxp-utils

If your project was created with Bolt UXP, the required UXP type packages (@adobe/premierepro, @types/photoshop, @adobe/cc-ext-uxp-types) are already included - no extra install needed.

If you're starting from scratch, install them yourself:

npm install --save-dev @adobe/cc-ext-uxp-types @adobe/premierepro @types/photoshop

Usage:

Three equivalent import styles, pick whichever fits your code style

Named imports:

//Premiere Pro
import { getActiveRoot, cloneSequence, forEachClip } from "bolt-uxp-utils/ppro";

const root = await getActiveRoot();
//photoshop
import { asModal, deselectAllLayers } from "bolt-uxp-utils/ps";

await asModal("My Command", async () => {
  await deselectAllLayers();
});

Default import (namespace style):

//Premiere Pro
import bolt from "bolt-uxp-utils/ppro";

const root = await bolt.getActiveRoot();
//photoshop
import bolt from "bolt-uxp-utils/ps";

await bolt.asModal("My Command", async () => {
  await bolt.deselectAllLayers();
});

Namespace import:

//Premiere Pro
import * as bolt from "bolt-uxp-utils/ppro";

const root = await bolt.getActiveRoot();
//photoshop
import * as bolt from "bolt-uxp-utils/ps";

await bolt.asModal("My Command", async () => {
  await bolt.deselectAllLayers();
});

Path B - without a bundler

UXP can't resolve npm package names at runtime - only relative paths. So we ship a setup command that copies the CommonJS files into your plugin folder, and you require() them by relative path.

Step 1 - install the package

npm install bolt-uxp-utils

Step 2 - copy the files into your plugin

npx bolt-uxp-utils setup

This creates a bolt-uxp-utils/ folder next to your manifest.json. It ships inside your final plugin package.

Step 3 - require it in your code

Destructured (CommonJS):

const { getActiveRoot } = require("./bolt-uxp-utils/ppro");
const { asModal, deselectAllLayers } = require("./bolt-uxp-utils/ps");

Namespace (CommonJS):

const bolt = require("./bolt-uxp-utils/ppro");
const root = await bolt.getActiveRoot();

Notes

Requires Adobe Premiere Pro 26.3.0+. Earlier versions used a different transaction API; helpers like cloneSequence, deleteItem, and setPrMetadata won't work on older builds.

Node version warning during install

Temporarily using the forked version of the Premiere Pro type @adobe/premierepro since the offical version requires Node 24.13.0+ as required, but is types-only at runtime - the constraint is overly strict. If yarn refuses to install, use yarn install --ignore-engines. npm warns and installs without issue.

Build outputs (for contributors)

| Folder | Format | Consumed via | | ------------- | ----------------------- | --------------------------------------- | | dist/esm/ | ES modules | import (bundlers, modern Node) | | dist/cjs/ | CommonJS | require() (vanilla UXP) | | dist/types/ | TypeScript declarations | Both - for autocomplete and type checks |

The exports field in package.json picks the right one automatically.

Develop

npm install
npm run build

License

MIT