P!npoint

Plugins

Packaging and Publishing

This page explains .ppplugin packages and official catalog generation.

Package Format

.ppplugin packages contain plugin files.

At minimum, a package needs:

  • manifest.json
  • the JavaScript file referenced by entry

Verify

npm run plugin:verify -- plugin-src/official/diff-impact-analyzer

Verification checks:

  • manifest schema
  • extension point allow list
  • permission allow list
  • permission coverage
  • entry file existence

Test

npm run plugin:test -- plugin-src/official/diff-impact-analyzer

plugin:test verifies the plugin and writes a test package to dist-plugin-registry/test-packages.

Pack

npm run plugin:pack -- plugin-src/official/diff-impact-analyzer

This creates a single plugin package.

Official Catalog

npm run release:plugin-catalog

This command packages only official plugins listed in plugin-src/catalog.json.

The output is:

  • dist-plugin-registry/catalog.json
  • dist-plugin-registry/packages/*.ppplugin

Public Pages Payload

The public Pages payload includes only plugins/catalog.json and plugins/packages/*.ppplugin.

plugins/test-packages must not be published.