Skip to main content
SpurtCommerce describes add-ons/plugins as a way to extend platform functionality. The v6 repository contains src/plugin-manager and an add-ons directory; inspect the target release to determine the supported plugin contract.

Before implementing a plugin

  • Confirm the plugin discovery/registration mechanism.
  • Identify supported lifecycle hooks, dependency injection/context, configuration format, and compatibility rules.
  • Check how plugin entities are registered and how plugin migrations are executed.
  • Define permissions, tenant isolation, logging, and failure behavior.
  • Confirm whether a capability is core, bundled add-on, or separately installed.

Safe extension principles

Prefer documented extension points over patching core files. Pin compatible versions, validate configuration at startup, isolate external calls, and provide install/upgrade/uninstall instructions. Never assume a v5 add-on package is compatible with v6.

Source map

Review src/plugin-manager, repository add-ons, package scripts, entity discovery configuration, and relevant tests. Publish a plugin API only after it is verified against code and an executable sample.