JUBELBUILD — DEVELOPER TOOLS
Library
Feature Analysis · Merge DEV ZIPs from tightly-coupled addons into the current build.
What the Library is for
Some architectures split functionality across a main plugin and one or more addon plugins. If your main plugin optionally integrates with an addon — a compliance fixer, an importer module, a reporting component — you can add that addon's DEV ZIP to the library, and JubelBuild includes its code in the build output. Its code is treated as part of the main plugin during the transformation.
Requirements for a library ZIP
- It must be a valid DEV plugin (Plugin Name contains " DEV").
- It must carry a valid HMAC signature (generated by JubelBuild when you previously built that plugin).
- Its slug must match a saved dataset in JubelBuild.
These requirements ensure only trusted, JubelBuild-managed code is included in library builds.
Two ways to add a project
Scan installed DEV plugins
The fastest way. JubelBuild scans the plugin directory and lists every installed plugin whose folder ends in -dev (and whose Plugin Name contains "DEV" and whose slug matches a saved dataset). Click + Add — no upload, no signature check; the build reads the files live from the server.
Upload DEV ZIP
For addons not installed on this server, or to pin a specific version: build the addon first (Steps 1–4), download its signed DEV ZIP from Step 4, then choose it here and click Upload & Validate. JubelBuild verifies signature and slug — valid gets a ✅ badge, invalid a ⚠️ warning.
Each entry in the library list shows its validation status (✅ / ⚠️), plugin name, version and slug, plus a ️ Remove (which removes the entry, not the file).
Automatic PRO-only detection
JubelBuild checks each library addon's dataset. If the addon has Create FREE Version unchecked (HAS_FREE = false), it has no free version — so JubelBuild automatically wraps every reference to that addon's slug in your main plugin inside [PRO]…[/PRO] during the build:
- The addon configuration code (e.g. in
addons-page.php) is removed from the FREE ZIP. - It remains in the PRO ZIP.
- You don't add
[PRO]tags around addon config manually — JubelBuild does it based on the dataset setting.
If the addon has a FREE version (HAS_FREE = true), its config is left unchanged in both builds. Slug accuracy matters: the wrapping searches for the addon's exact slug (e.g. whoismember-activitylog) in your PHP files — it must match the slug used in your addon configuration (e.g. the 'slug' key in $available_addons), or the wrapping won't apply.
Build integration
When you start the build, library ZIPs are included in the transformation: their [PRO] blocks are stripped for FREE, their headers are patched, and their code is packaged into the final ZIPs alongside the main plugin. Note that the Library is a build-time concept — it physically merges code and does not create WordPress runtime plugin dependencies. Use it only for tightly coupled addons that always ship together with the main plugin.
Ship coupled addons as one
Merge trusted DEV addons into the build — with PRO-only wrapping handled automatically.