Publishing

npm run build
npx @notch-monster/plugin-cli pack dist     # checks it like the marketplace, writes <id>-<version>.notchplugin
npx @notch-monster/plugin-cli login         # your email + a 6-digit code, and a publisher name
npx @notch-monster/plugin-cli submit dist   # packs and uploads, then waits for review
npx @notch-monster/plugin-cli status        # pending / approved / rejected, with notes

The starter has these as npm run pack and npm run submit.

Review

A person reviews every version. They read your code, so:

• ship readable source, or include source maps;
• don’t obfuscate your code, because obfuscated plugins are rejected;
• be ready to explain anything flagged at submit time (eval, network calls outside notch.net, minified bundles).

After approval

The marketplace signs that exact package and lists it on notch.monster/plugins and in the app (Settings → Marketplace).

• Updates: bump version and submit again. Users get the update within 6 hours. If an update asks for new permissions or domains, it waits for each user to approve it.
• Your id: it belongs to you after your first submission.
• Blocking: if a version is found to be harmful, it’s blocked and apps turn it off.