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

create-adobe-extension

v1.2.0

Published

This package provides a CLI tool to create Adobe CEP Extensions.

Readme

Create Adobe Extension

This package provides a CLI tool to create Adobe CEP Extensions.

Features

  • Create Adobe CEP Extension Bundles without needing to download them from the CEP-Resources Github repository.
  • Add new extensions to existing Adobe CEP Extension Bundles.
  • Automatically generate .debug files based on your inputs.

Usage

Navigate to the Folder you want to create your extension in.

By default the tool checks to see if you're creating an extension in the official Adobe extensions folder. If not, it will give you a warning asking if you want to continue.

These extension folders are found at:

  • System extension folder

    • Win(x64): C:\Program Files (x86)\Common Files\Adobe\CEP\extensions, and C:\Program Files\Common Files\Adobe\CEP\extensions (since CEP 6.1)
    • macOS: /Library/Application Support/Adobe/CEP/extensions
  • Per-user extension folder

    • Win: C:\Users\<USERNAME>\AppData\Roaming\Adobe\CEP/extensions
    • macOS: ~/Library/Application Support/Adobe/CEP/extensions

Now run command:

$ npx create-adobe-extension.

The tool will request information about your extension, then create the necessary files for your extension.

Flags

  • --options: Display a list of all flags available for create-adobe-extension.

  • --add: Add a new extension to an existing extension bundle (make sure you're inside the folder of the bundle you'd like to add to before running).

  • --folder-check: Enable/disable a warning when creating an extension outside of standard Adobe Extensions folder.

User Responses

  • Project Name: Name of the extension Folder and the first extension in this bundle.

  • Bundle ID: Must begin with "com." i.e.: "com.test".

  • Extension ID: Must begin with your Bundle ID. i.e.: "com.test.panel".

  • Extension Version: Extension version identifier. Set to 1.0.0 by default.

  • CSXS Version: Sets the version of CSXS this extension will use. Set by default to the newest version.

  • Extension Type: Indicates whether the this is a Panel, ModalDialog, Modless or Custom Extension.

  • Program(s): Defines which program or programs this extension will open in.

  • Program Version(s): Sets the version or versions this extension will run in. To set a range, seperate two numbers with a comma. Set by default to "1.0,99.0".

  • Enable Node.js: Enable or disable the use of Node.js in your extension.

  • Enable Debugging: Set whether or not to enable debugging. If enabled, this tool will create a .debug file with the appropriate extension info and adds a function to your javascript file that reloads your jsx script every time your javascript file is initialized (use in conjunction with Adobe Live Reload for an optimal debugging experience).

Changelog

v1.2.0 (2022-04-25)

Added

  • Added --add flag which allows for the creation of new extensions within an existing extension bundle.
  • Added --options flag which displays all flags available in this package.
  • Added --folder-check flag which enables/disables a check to warn users when they are creating an extension outside of the official Adobe extensions folders.

Changes

  • Updated README to clarify where the extension folders are located, what the package checks for and how to disable the checking.

Removed

  • Removed Ascii art title because it was annoying me when I used this package.

v1.1.3 (2022-04-19)

Changes

  • Changed Ascii art title to match npm package title.

v1.1.2 (2022-04-19)

Changes

  • Changed method of detecting the current working folder for CEP Extension fold check.

v1.1.0 (2022-04-19)

Added

  • Added README file
  • Added check for whether user is in CEP Extensions folder
  • Added Adobe Live Reload Ascii art