Package and publish
Publishing puts a version of your plugin on the marketplace at e-volv.io, where Jacker users can find and install it. A version is listed as soon as it passes the marketplace’s checks; there’s no manual review.
Before you begin
- Test the plugin. See Test a plugin in Jacker.
- For each
binaryprogram, build every platform’s artifact and put it in the plugin’sartifacts/folder under the name the manifest gives it. - Have an e-volv.io account with a verified email address.
Package
Run:
jacker-plugin pack PLUGIN_FOLDER --out DIST_FOLDER
Replace PLUGIN_FOLDER with your plugin and DIST_FOLDER with an empty folder. pack validates the plugin first and writes nothing if it fails.
DIST_FOLDER then contains:
plugin.tgz: everything in the plugin folder exceptartifacts/,node_modules/,.git/, and.DS_Store.- Each platform artifact.
files.json: the plugin’s id and version, and the SHA-256 hash of each file. The marketplace signs this list, and Jacker checks the signature and every hash before it installs.
The archive is reproducible: the same files give the same hash on any machine.
Limits: plugin.tgz holds at most 2,000 files and 20 MB; each artifact is at most 150 MB; a version is at most 400 MB.
Publish
You publish from the Jacker plugin publishing page in your e-volv.io account.
- On e-volv.io, create a publisher. Its slug must match the part of your plugin id before the dot.
- Upload every file in
DIST_FOLDER.
If the marketplace refuses the version, the publishing page shows why. The marketplace rejects a version if:
- A file’s hash doesn’t match
files.json, or a file is missing or extra. - The archive contains a link, an absolute path, or
... - The manifest is invalid, or its id and version differ from
files.json. - You don’t own the publisher the id names.
- The version isn’t greater than your latest.
- A file the manifest names, or an artifact, is missing.
- A file looks like it contains a secret key.
- You’ve published 10 versions of the plugin, or 20 new plugins, today.
Update a plugin
Publish a new version with a greater version. Users see Update to VERSION on the plugin’s page; Jacker doesn’t update plugins on its own.
Withdraw a version
You can delist a version or the whole plugin from your publisher page. Delisted plugins don’t appear in search; users who installed them keep them.
What’s next
See Marketplace rules.