Bunny Stream Laravel Package

Technical Evaluation

This is the baseline assessment; no prior evaluation exists. The only evidence available is the 1.1.2 release note, so conclusions below are scoped accordingly and flagged where verification is needed.

Architecture fit. The package is a Statamic add-on delivered as a Laravel package. Its user-facing capability is a control-panel focal-point preview, which is a client-side editorial UX feature rather than a runtime/backend service. The 1.1.2 change — isolating the control-panel bundle from browser globals — indicates the bundle previously shared or consumed window-level state. That is a common source of cross-add-on collisions in Statamic's CP, and the isolation is an architectural improvement. Fit is strong for teams already standardized on Statamic; the package has no value for plain Laravel applications.

Integration feasibility. Install path is standard Composer plus Statamic add-on discovery. The release explicitly states no configuration changes, which implies a drop-in patch. The main feasibility question is the declared support matrix (Statamic 5 and 6, and by extension Laravel/PHP versions) in composer.json.

Technical risk. Low to moderate. The change is a patch-level CP fix. Stated risk: Statamic 5 behavior is unchanged, but "unchanged" should be verified in a staging CP rather than assumed. Secondary risk: any local custom scripts or other add-ons that implicitly relied on the previous global exposure could regress; the isolation is deliberately narrowing, so this is a feature, not a defect, but it is a behavioral surface change. Asset-publishing/cache-busting and CSP policies are the usual operational failure points for CP bundle changes.

Key questions.

• What is the supported matrix for Statamic, Laravel, PHP, and browser versions?
• Is 1.1.2 a minimal patch, or does it carry unrelated changes bundled into the release?
• What CP test coverage exists for focal-point previews across supported browsers?
• Does the add-on publish compiled assets that require vendor:publish or cache clearing on upgrade?
• Who maintains the package, what is the release cadence, license, and security-disclosure policy?
• Did the global-isolation change break any documented extension point?

Integration Approach

Stack fit. Fits Statamic 5/6 projects on Laravel. Installation is Composer-based; the CP bundle is a front-end asset. It does not alter content storage or the delivery API, so it sits cleanly alongside existing add-ons provided the CP bundle isolation holds.

Migration path. From 1.1.1 to 1.1.2: composer update with the version pinned in composer.lock; no config migration and no data migration. For teams moving to Statamic 6, sequence the CMS upgrade and this add-on patch together so focal-point previews are validated as part of the same change window.

Compatibility. Statamic 5 behavior is explicitly unchanged; Statamic 6 focal-point previews are the targeted fix. Verify PHP/Laravel constraints before committing, and confirm whether the 1.1.x line is the supported line for Statamic 6.

Sequencing.

1. Pin and review the package constraint and changelog.
2. Upgrade in a staging environment with representative content and both supported Statamic majors if the team runs a mixed estate.
3. Open the CP, exercise focal-point previews, and check the browser console for errors or CSP violations.
4. Clear CP/asset caches and confirm the new bundle is served.
5. Roll out to production with a pinned rollback version.

Operational Impact

Maintenance. Low recurring effort at patch level. The real maintenance cost is tracking Statamic major releases; this release demonstrates the add-on must be updated in step with the CMS.

Support. The timely Statamic 6 fix is a positive signal on maintainer responsiveness. Confirm the support channel and whether fixes are backported to older lines before relying on it for editorial-critical workflows.

Scaling. No backend or delivery scaling impact. The change affects only control-panel assets served to editors; load is negligible relative to content delivery.

Failure modes. Most likely failures are a blank or broken focal-point preview in the CP, JavaScript console errors, CSP blocking the isolated bundle, stale published assets after upgrade, and — least likely — breakage in custom scripts that depended on previously exposed globals. Rollback is a version pin to the prior release; no data rollback is required.

Ramp-up. Minimal for developers familiar with Statamic add-ons. For content editors, the feature is a preview aid, so ramp-up is limited to a short verification pass during rollout.