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

create-zxp

v0.1.0

Published

Creates Adobe ZXP Packages.

Downloads

30

Readme

create-zxp

What

Creates Adobe ZXP Packages with zero configuration.

Install

With Yarn:

$ yarn add --dev create-zxp

With NPM:

$ npm install --save-dev create-zxp

Usage

CLI

cep-packager [input] [options]

Options:

  --name <name>                   name of the zxp. default: package.json name or process.env.ZXP_NAME
  --version <version>             version of the zxp. default: package.json version or process.env.ZXP_VERSION
  --out-dir <out-dir>             output directory. default: archive
  --cert-file <file>              certificate file. default: self-sign or process.env.ZXP_CERT
  --cert-password <password>      certificate password. default: password or process.env.ZXP_CERT_PASSWORD
  --cert-country <country>        certificate country. default: US or process.env.ZXP_CERT_COUNTRY
  --cert-province <province>      certificate province. default: CA or process.env.ZXP_CERT_PROVINCE
  --cert-org <org>                certificate org. default: "My Company" or process.env.ZXP_CERT_ORG
  --cert-name <name>              certificate name. default: "My Company" or process.env.ZXP_CERT_NAME
  --cert-timestamp <timestamp>    certificate timestamp. default: process.env.ZXP_CERT_TIMESTAMP
  --silent                        silence output

Example:

Assuming a production build of your extension is in the build directory and doesn't contain symbolic links:

$ create-zxp ./build

Will create a self-signed .zxp file in ./archives.

Node API

const createZXP = require('create-zxp')

createZXP({
  inputDirectory: string            // input source for zxp
  outputFile: string                // output file
  tempDir: string                   // temp directory to use for building
  name: string                      // name of the zxp
  version: string                   // version of the zxp
  certFile?: string                 // certificate to sign zxp with
  certPassword?: string             // certificate password
  certCountry?: string              // certificate country
  certProvince?: string             // certificate province
  certOrg?: string                  // certificate org
  certName?: string                 // certificate name
  certTimestamp?: string            // certificate timestamp
  silent?: boolean                  // silent stdout
}).catch(e => console.error(e))