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

rollup-plugin-zxp

v1.1.0

Published

Create a signed .ZXP extension for Adobe CEP plugins

Downloads

9

Readme

rollup-plugin-zxp

A Rollup wrapper of zxp-sign-cmd to bundle your Rollup output into a signed .zxp file, made for Adobe CEP extensions.

Installation

npm install rollup-plugin-zxp

Setup

With Vite (vite.config.js):

import { defineConfig } from 'vite';
import zxp from 'rollup-plugin-zxp';

export default defineConfig({
    build: {
        rollupOptions: {
            plugins: [
                zxp(), // Options required, see below
            ],
        },
    }
});

With Rollup (rollup.config.js):

import zxp from 'rollup-plugin-zxp';

export default {
    plugins: [
        zxp(), // Options required, see below
    ],
};

Recommended Use

Create a .env in your project root and add the following variables:

CERT_COUNTRY=US
CERT_PROVINCE=CA 
CERT_ORG=My Company
CERT_NAME=My Name
CERT_PASSWORD=myPassword
[email protected]

Install the dotenv package to load the variables from the .env file:

npm install dotenv --save

At the top of your rollup.config.js or vite.config.js file import and initialize dotenv

import * as dotenv from 'dotenv';
dotenv.config();

Later on inside the same file, pass your information to the plugin:

zxp({
    selfSignedCert: {
        country: process.env.CERT_COUNTRY,
        province: process.env.CERT_PROVINCE,
        org: process.env.CERT_ORG,
        name: process.env.CERT_NAME,
        email: process.env.CERT_EMAIL,
        password: process.env.CERT_PASSWORD
    },
    sign: {
        password: process.env.CERT_PASSWORD
    },
    gitIgnore: [`.env`, `*.p12`]
})

To build and sign your extension, run npm run build.

What and When?

To create a certificate only:

zxp({
    selfSignedCert: {
        country: process.env.CERT_COUNTRY,
        province: process.env.CERT_PROVINCE,
        org: process.env.CERT_ORG,
        name: process.env.CERT_NAME,
        email: process.env.CERT_EMAIL,
        password: process.env.CERT_PASSWORD,
        output: 'path/to/cert.p12'
    },
})

To sign with an existing certificate:

zxp({
    sign: {
        cert: 'path/to/cert.p12',
        password: process.env.CERT_PASSWORD
    }
})

To create a certificate and use it for signing (recommended).

zxp({
    selfSignedCert: {
        country: process.env.CERT_COUNTRY,
        province: process.env.CERT_PROVINCE,
        org: process.env.CERT_ORG,
        name: process.env.CERT_NAME,
        email: process.env.CERT_EMAIL,
        password: process.env.CERT_PASSWORD // Password must match
    },
    sign: {
        password: process.env.CERT_PASSWORD // Password must match
    }
})

Since we're dealing with personal information in your .env file, it is recommended that you instruct the plugin to create or edit a .gitignore file with the following keys:

zxp({
    gitIgnore: [`.env`, `*.p12`]
})

Now, the .env file and the .p12 certificate file will be ignored by Git.

Options

overrideCert? - If true, it will override the certificate file if it already exists (default: true)

overrideZXP? - If true, it will override the .zxp file if it already exists (default: true)

selfSignedCert

Type: object

  • country - The country of the certificate owner.
  • province - The province of the certificate owner.
  • org - The organization of the certificate owner.
  • name - The name of the certificate owner.
  • email - The email of the certificate owner.
  • password - The password of the certificate owner.
  • state? - The state of the certificate owner.
  • city? - The city of the certificate owner.
  • output? - The path to the .p12 certificate file (default: .secret/cert.p12)

sign

Type: object

  • password - The password of the certificate owner.
  • input? - The dist folder to be signed (default: dist)
  • output? - The path to the .zxp file to be signed (default: working directory)
  • cert? - The path to the .p12 certificate file (default: certOptions.output)

License

MIT