JUBELBUILD — DEVELOPER TOOLS
Parallel Lint
PHP syntax checker for JubelBuild — detects parse errors before deployment.
Catch parse errors before deployment
Parallel Lint is an optional add-on for JubelBuild. When active, every build target — DEV, PRO and FREE — is checked for PHP parse errors before the ZIP is created, so syntax errors introduced by the transformation never reach production.
Parallel Lint checks the syntax of your PHP code in parallel, drastically reducing analysis time compared to traditional methods. For developers, identifying syntax errors early is crucial — especially during refactoring, updates, and when working with legacy code.
How it works
- Checked before packaging: the PHP syntax of every file in your build directory is verified before the ZIP is created.
- Native
php -l: each.phpfile is linted with PHP's own syntax check (skippingvendor/). - Debug log: any parse errors are logged to
/wp-content/bh-parallellint-debug.log. - Fully integrated: runs inside the JubelBuild build pipeline across all three targets — DEV, PRO and FREE.
- Results in Step 4: the outcome is shown in Step 4 after each build.
Requirements
- WordPress 5.8 or higher (tested up to 7.0).
- PHP 7.4 or higher.
- The active core plugin JubelBuild (Pro).
- Current version 1.1.6 · GPLv2 or later.
FAQ
What does it check?
The PHP syntax of every .php file in the build directory (excluding vendor/), using php -l — so parse errors are caught before a ZIP is ever created.
Where are errors logged?
To /wp-content/bh-parallellint-debug.log; the result is also surfaced in Step 4 after each build.
Which builds are checked?
All three pipeline targets — DEV, PRO and FREE.
Does it require JubelBuild?
Yes. Parallel Lint is integrated into the JubelBuild build pipeline and requires the active core plugin (Pro).
Never ship a broken ZIP again
Every build target is linted before packaging — parse errors surface in Step 4, never in production.